Source type
Drip Source Configuration
Drip sources receive subscriber, campaign, tag, delivery, open, click, bounce, complaint, and lead events.
Drip configuration
Create a Drip source, keep POST enabled, and provide the configured Webhook URL Secret values for provider signature. FastHook uses these settings to validate each Drip delivery before it enters the routing workflow.
Source TypeDRIP
Allowed methodsPOST
AuthenticationProvider signature
Credential fieldsWebhook URL Secret
{
"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"]
}
}Drip request contract
Drip does not publish a payload-signature scheme. FastHook checks a secret query parameter and removes it from stored request metadata.
Drip headers
Preserve the source authentication values when sending Drip 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 Drip source does not require provider-specific signature headers. Use its configured source auth fields and inspect rejected requests if Drip does not match the saved credentials.
Drip setup
- Create a Drip source and choose a long random Webhook URL Secret.
- Append ?secret=YOUR_SECRET to the FastHook Source URL before adding it in Drip.
- Select only the subscriber and engagement events needed by the workflow.
- Enable subscriber.received_email only when the downstream system can handle its volume.