Source type
Hygraph Source Configuration
Hygraph sources receive content model and content entry webhooks across Hygraph's supported methods with signed gcms-signature verification.
Hygraph configuration
Create a Hygraph source, keep GET and POST and PUT and DELETE enabled, and provide the configured Secret Key values for provider signature. FastHook uses these settings to validate each Hygraph delivery before it enters the routing workflow.
Source TypeHYGRAPH
Allowed methodsGET, POST, PUT, DELETE
AuthenticationProvider signature
Credential fieldsSecret Key
{
"type": "HYGRAPH",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "HYGRAPH",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["GET","POST","PUT","DELETE"]
}
}Hygraph request contract
FastHook parses gcms-signature, builds the Hygraph signed JSON envelope with body, environment, and timestamp, then verifies the base64 HMAC-SHA256 signature.
Hygraph headers
Preserve gcms-signature when sending Hygraph 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.
gcms-signatureContains sign, env, and t parameters.
Hygraph setup
- Create a Hygraph webhook and use the generated FastHook Source URL.
- Paste the Hygraph secret key into FastHook.
- Keep the broader GET/POST/PUT/DELETE method set because Hygraph can use multiple methods.