Skip to main content

EventToWebHookConfigUpdateInput

Input for updating webhook event action configurations.

Extends base event action updates with webhook-specific fields. Only provided fields will be updated, others remain unchanged.

input EventToWebHookConfigUpdateInput {
names: [LocalizedStringInput!]
trigger: EventTrigger
code: String
channelIds: [Int!]
url: String
signatureSalt: String
basicAuthUsername: String
basicAuthPassword: String
}

Fields​

EventToWebHookConfigUpdateInput.names ● [LocalizedStringInput!] list input​

Updated display names in multiple languages.

When provided, must contain at least one localized name. Each language entry must be unique and properly validated.

EventToWebHookConfigUpdateInput.trigger ● EventTrigger enum​

System event that activates this action configuration.

Defines which event type will cause this automation to execute, enabling event-driven workflow processing.

EventToWebHookConfigUpdateInput.code ● String scalar​

Updated custom event code for CUSTOM_EVENT triggers.

Maximum length of 64 characters. Used to identify which configurations to execute for custom events.

EventToWebHookConfigUpdateInput.channelIds ● [Int!] list scalar​

Array of channel identifiers for filtering event action configurations.

Used to restrict event action configurations to specific communication channels. When omitted, returns all channels.

EventToWebHookConfigUpdateInput.url ● String scalar​

Updated HTTPS webhook endpoint URL.

Must be a valid HTTPS URL with protocol specified. Only secure HTTPS connections are allowed for webhook delivery to ensure data security.

EventToWebHookConfigUpdateInput.signatureSalt ● String scalar​

The salt used to generate HMAC-SHA256 signature for webhook authentication.

When configured, the webhook will include an 'X-Propeller-Signature' header with format 'sha256=<hex_signature>'.

To verify the signature:

  1. JSON stringify the payload
  2. Generate HMAC-SHA256 using this salt and the stringified payload
  3. Compare with the received signature using crypto.timingSafeEqual() to prevent timing attacks

Example (Node.js): const expectedSig = crypto.createHmac('sha256', salt).update(JSON.stringify(payload), 'utf8').digest('hex'); const receivedSig = signature.replace('sha256=', ''); return crypto.timingSafeEqual(Buffer.from(expectedSig, 'hex'), Buffer.from(receivedSig, 'hex'));

EventToWebHookConfigUpdateInput.basicAuthUsername ● String scalar​

Updated basic authentication username.

When provided, must be used together with basicAuthPassword. Both username and password must be provided or both must be omitted for valid authentication configuration.

EventToWebHookConfigUpdateInput.basicAuthPassword ● String scalar​

Updated basic authentication password.

When provided, must be used together with basicAuthUsername. Both username and password must be provided or both must be omitted for valid authentication configuration.

Member Of​

eventToWebHookConfigUpdate mutation