Webhook
Trigger workflow execution when an external system sends an HTTP request to a Scrydon-generated URL.
The Webhook block generates a unique HTTP endpoint. Any external service that can send an HTTP POST request can trigger your workflow.
How it works
- Add a Webhook block to your workflow.
- A unique webhook URL is generated for that block — copy it from the block's Trigger Link field.
- Configure your external service (GitHub, Stripe, any custom system) to POST to that URL.
- When the request arrives, the workflow starts and the request body, headers, method, and query parameters are injected as block outputs.
Testing in Development
You don't need to deploy or promote to test a webhook. In the writable Development environment, calling the webhook URL runs the live/draft workflow — exactly what's on the canvas — so you can iterate and test end to end as you build.
When you promote the workflow to Staging or Production (read-only environments), the webhook there runs the deployed snapshot instead, and requires an active deployment version. Each environment has its own webhook URL. See Triggers → Environments and testing for the full model.
Available variables
Reference the incoming request in downstream blocks using the block's name as the prefix:
| Variable | Description |
|---|---|
<webhook1.payload> | Full request body (parsed JSON or raw string) |
<webhook1.headers> | Request headers as a JSON object |
<webhook1.method> | HTTP method (POST, PUT, etc.) |
<webhook1.query> | Query string parameters as a JSON object |
Replace webhook1 with whatever name you gave the block.
Authentication
Webhook endpoints accept unauthenticated POSTs by default. To restrict access, configure a secret in the block's webhook configuration. Scrydon will verify an X-Scrydon-Secret header on incoming requests and reject requests that don't match.
curl -X POST "https://app.scrydon.com/api/webhooks/trigger/{path}" \
-H "Content-Type: application/json" \
-H "X-Scrydon-Secret: {your-secret}" \
-d '{"event": "order.created", "orderId": "42"}'Vendor-specific triggers
For services with a dedicated Scrydon integration (GitHub, Microsoft Graph, Atlassian, etc.), prefer the vendor's trigger block over the generic Webhook block. Vendor triggers parse and validate the event payload automatically and surface typed variables.
See Vendors for the full list of integrations with trigger support.
Webhook blocks are receive-only. They start the workflow but cannot send a response back to the caller beyond a standard HTTP 200 acknowledgement. To return data to a caller, use the Start (API) trigger instead.