Source type
Mailgun Source Configuration
Mailgun sources receive event and tracking webhooks and verify the Mailgun timestamp, token, and signature fields.
Mailgun configuration
Create a Mailgun source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured HTTP Signing Key values for provider signature. FastHook uses these settings to validate each Mailgun delivery before it enters the routing workflow.
Source TypeMAILGUN
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsHTTP Signing Key
{
"type": "MAILGUN",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "MAILGUN",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Mailgun request contract
FastHook computes HMAC-SHA256 over timestamp + token and compares it with the Mailgun signature field.
Mailgun headers
Preserve signature.timestamp, signature.token, signature.signature when sending Mailgun 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.
signature.timestampTimestamp field in JSON or form body.
signature.tokenMailgun token field in JSON or form body.
signature.signatureHMAC-SHA256 hex signature field.
Mailgun setup
- Point Mailgun event webhooks at the FastHook Source URL.
- Paste the Mailgun HTTP signing key into FastHook.
- Use connection filters if delivery, bounce, complaint, and open events should go to different destinations.