Source type

Zendesk Source

Zendesk sources receive Support, Guide, Gather, and Messaging webhook activity with timestamped Zendesk signature verification.

ZENDESKPOST, PUT, PATCH, DELETEWebhook Signing SecretProductivity
Zendesk webhooks documentationAll source types
Zendesk sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.ZendeskProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLZENDESKProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.
FastHook keeps the provider-facing contract on the source. Accepted requests are stored before routing, while rejected requests keep enough evidence to debug signature, method, and challenge failures.

When to use this source type

Choose the ZENDESK source type when Zendesk is the system sending webhook requests into FastHook. The source type keeps sender-specific setup close to the source: accepted methods, verification headers, challenge handling, and the exact credential fields are documented together so operators do not need to translate a generic HMAC form into a provider-specific contract.

FastHook verifies the source before accepted traffic is queued. A valid request is stored with verified: true, then connections route it to destinations. A bad signature, wrong token, or missing provider header is rejected as SOURCE_AUTH_FAILED. A method outside the allowed set is rejected as SOURCE_METHOD_NOT_ALLOWED.

FastHook configuration

In the dashboard, create a source, set Source Type to Zendesk, keep Authenticate enabled when verification is required, and fill the fields below.

Source Type

ZENDESK

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Webhook Signing Secret

Copy this value from Zendesk and store it on the FastHook source.

{
  "type": "ZENDESK",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "ZENDESK"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

HTTP methods

This source accepts only the methods listed below. Keep the set narrow so provider mistakes and accidental test calls are visible as rejected requests instead of being silently accepted.

POSTPUTPATCHDELETE

Headers and verification

FastHook verifies the provider-specific values below before the request is accepted. The comparison is done against the raw inbound request body or the exact provider-specific signing input described here.

x-zendesk-webhook-signature

Base64 HMAC-SHA256 signature.

x-zendesk-webhook-signature-timestamp

ISO timestamp concatenated with the raw body before signing.

FastHook signs timestamp + raw body with HMAC-SHA256 and compares the base64 digest to x-zendesk-webhook-signature.

Provider setup checklist

  1. Create a Zendesk webhook with the FastHook Source URL.
  2. Paste the Zendesk signing secret into FastHook.
  3. Use tags, ticket ids, or event types for downstream routing.
  4. Open Zendesk webhooks documentation when you need the provider's event list, dashboard steps, or retry policy.

Troubleshooting

  • No request appears: the provider is not calling the generated FastHook Source URL, the source URL was copied before saving, or the provider has not completed its setup validation.
  • 405 method rejected: the provider sent a method outside POST, PUT, PATCH, DELETE. Edit the source only if the provider documentation says that method is expected.
  • 401 source auth failed: check the configured FastHook field, the provider signing secret, and the header names listed on this page.
  • Signature mismatch: make sure the provider signs the same public Source URL it calls and that no proxy, parser, or manual resend changed the raw request body before FastHook received it.

Related docs