Source type
Notion Source Configuration
Notion sources receive page and database activity webhooks and verify each payload with the webhook verification token.
Notion configuration
Create a Notion source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Verification Token values for provider signature. FastHook uses these settings to validate each Notion delivery before it enters the routing workflow.
Source TypeNOTION
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsVerification Token
{
"type": "NOTION",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "NOTION",
"webhook_signing_secret": "verification-token"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Notion request contract
FastHook computes sha256= HMAC-SHA256 over the raw body with the Notion verification token and compares it with x-notion-signature.
Notion headers
Preserve x-notion-signature when sending Notion 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.
x-notion-signaturesha256= HMAC-SHA256 signature over the raw request body.
Notion setup
- Create a Notion webhook subscription with the generated FastHook Source URL.
- Copy the one-time verification_token from Notion into FastHook.
- Use event type and page or database ids for routing and deduplication.
Notion routing hints
- Notion activity webhooks usually route by event type, workspace, page id, or database id.
- Use page or database ids near the receiver when repeated deliveries can create side effects.