ActiveTrail Source Configuration

ActiveTrail configuration

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

{
  "type": "ACTIVETRAIL",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "ACTIVETRAIL",
      "webhook_signing_secret": "long-random-url-secret",
      "query_parameter_name": "secret"
    },
    "allowed_http_methods": ["POST"]
  }
}

ActiveTrail request contract

ActiveTrail does not publish a standard webhook signature. FastHook checks the callback URL secret and removes it from stored request metadata.

ActiveTrail headers

Preserve the source authentication values when sending ActiveTrail 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.

The ActiveTrail source does not require provider-specific signature headers. Use its configured source auth fields and inspect rejected requests if ActiveTrail does not match the saved credentials.

ActiveTrail setup

1. Create an ActiveTrail source and choose a long random Webhook URL Secret.
2. Append ?secret=YOUR_SECRET to the Source URL.
3. In ActiveTrail Settings, open Events and use the complete URL for each required contact event.
4. Run ActiveTrail's Test Event action before connecting production destinations.

Continue with ActiveTrail

• ActiveTrail REST API and webhook guide
• Source operations and troubleshooting