Asana Source Configuration

Asana configuration

Create a Asana source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each Asana delivery before it enters the routing workflow.

{
  "type": "ASANA",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "ASANA",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Hook-secret handshake before event delivery

1. Asana sends an initial request with x-hook-secret.
2. FastHook returns the same x-hook-secret header in a 200 response.
3. Later Asana event requests are signed with x-hook-signature and verified before queueing.

Asana request contract

FastHook answers the x-hook-secret handshake and verifies later x-hook-signature HMAC-SHA256 values over the raw body.

Special response: Handshake requests receive an empty 200 response with the same x-hook-secret header.

Asana headers

Preserve x-hook-secret, x-hook-signature when sending Asana test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

Asana setup

1. Create an Asana webhook with the FastHook Source URL.
2. During the handshake, FastHook returns the x-hook-secret header Asana sends.
3. Store or configure the learned hook secret so later POST requests can be verified.

Continue with Asana

• Asana webhooks documentation
• Source operations and troubleshooting