Integrations

Drip Webhooks Integration

Drip webhooks send subscriber lifecycle, campaign, tag, delivery, engagement, bounce, complaint, and lead events as JSON POST requests.

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

How the integration works

  • Events include subscriber.created, subscribed, unsubscribed, applied_tag, opened_email, clicked_email, bounced, and complained.
  • Drip's public documentation does not define a cryptographic payload-signature scheme.
  • FastHook protects the endpoint with a secret query value and removes that secret from stored request metadata.
  • Drip can retry rate-limited webhook delivery for up to three days.

Create the FastHook source

Create DRIP source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Drip Webhooks Integration",
    "type": "DRIP",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "DRIP",
        "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 a DRIP source and choose a long random URL secret.
  2. Append ?secret=YOUR_SECRET to the generated Source URL.
  3. Create the webhook in Drip and select only the events the workflow needs.
  4. Send a subscriber test event, inspect the payload, and connect the destination.

Production notes

  • Keep the complete secret URL out of screenshots, analytics, and tickets.
  • Enable subscriber.received_email only when downstream capacity is sufficient.
  • Use event, account_id, occurred_at, and subscriber identifiers for routing and deduplication.

Related documentation