Synthflow signs every webhook payload with an HMAC using your shared secret key. The resulting signature, included in the HTTP_SYNTHFLOW_SIGNATURE header, lets you confirm that the payload came from Synthflow and was not altered in transit.
Signature validation ensures authenticity (the sender is Synthflow) and integrity (the payload hasn’t been modified).
While TLS (HTTPS) protects against eavesdropping and tampering during transit, it does not guarantee that the request is genuinely coming from Synthflow. Without signature validation, an attacker who discovers or guesses your webhook URL can send forged payloads. These spoofed calls could trigger workflows, write bad data, or corrupt your system.
Without a secret key, for example, a malicious actor could create fraudulent appointments in your CRM by replaying fake call payloads.
Go to Settings > Security > Webhooks and generate a secret key. Synthflow uses this key to generate a signature that is included in the webhook HTTP header for every call.
Send the signature header with every webhook. Synthflow uses the call_id as the payload and signs it with your secret key before adding it to the HTTP_SYNTHFLOW_SIGNATURE header.
Synthflow includes this header on both the inbound webhook and the post-call webhook.
Verify the signature on your side using the same secret key and the received call_id.
If the output is True, the payload originated from Synthflow and was not altered in transit.