Integrations

ActiveTrail Webhooks Integration

ActiveTrail account Events can call an external URL when contact and subscriber information changes. FastHook provides a protected receiver and durable delivery evidence.

Capture the original request first, enforce the available trust boundary, then route and replay from durable evidence.

How the integration works

  • ActiveTrail configures outgoing callbacks under Settings and Events.
  • The provider offers a Test Event action for validating the receiver URL.
  • ActiveTrail does not publish a standard cryptographic signature for these events.
  • FastHook checks a secret query value and removes it from stored request metadata.

Create the FastHook source

Create ACTIVETRAIL source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "ActiveTrail Webhooks Integration",
    "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"]
    }
  }'

Append ?secret=YOUR_SECRET to the generated Source URL before saving it in the provider.

Setup

  1. Create an ACTIVETRAIL source and choose a long random URL secret.
  2. Append ?secret=YOUR_SECRET to the generated Source URL.
  3. In ActiveTrail Settings, add the complete URL to each required Event callback.
  4. Run Test Event, inspect the contact fields, and connect the required destination.

Production notes

  • Keep the callback URL secret because the provider does not publish a payload signature.
  • Treat subscriber fields and email activity as personal data.
  • Use stable contact identifiers when deduplicating changes.

Related documentation