With the Webhook destination, Sheetgo can push your connection results directly to any external service every time a connection runs. Instead of sending data only to spreadsheets or databases, you can deliver real-time updates straight to a custom API or third-party webhook — automating the steps that come after your data is processed.
Why use it
A Webhook destination removes manual data-transfer steps, letting you connect a workflow directly to external systems and trigger downstream processes automatically — every run delivers fresh data to the services that depend on it.
Note: The Webhook destination is currently in beta.
What you can do
Choose Webhook as a destination when building a workflow connection.
Configure the destination URL, HTTP method (POST, PUT, PATCH, or DELETE), and custom headers.
Define a custom request body template using placeholder variables to format the payload.
View webhook destinations as dedicated nodes in the workflow network view, and reopen or edit them at any time.
Set up a Webhook destination
Create or edit a workflow connection and choose a source as usual.
At the destination step, under Apps & services, select Webhook.
In Request URL, choose the HTTP method and paste the target endpoint URL.
The method dropdown supports POST, PUT, PATCH, and DELETE.
In Headers (JSON), add any headers your endpoint requires. A
Content-Type: application/jsonheader is included by default.In Request body, define the payload template. The body is rendered when the connection runs — reference your output with
DATA(the full table) orROWS(one object per record), and workflow fields likeworkflow_id.
Tip: Don't wrap placeholders in extra quotes, and avoid trailing commas between repeated items.
Click Review automation, then save the connection. Each time it runs, Sheetgo sends the rendered request to your endpoint.