Shipfox
IntegrationsCustom webhook

Custom webhook events

See how a custom webhook starts a workflow and what the event contains.

Shipfox accepts JSON, form, and plain-text bodies. Each accepted request gets a 202 Accepted response with a delivery_id. Give retries the same X-Delivery-ID header. Shipfox creates an ID when the header is missing.

Event catalog

Custom webhook triggers use only source. Use your custom webhook integration connection slug instead of deploy_hook.

Events
1in 1 group
Learn more
Fields appear below.

Requests

1 event

Requests sent to your custom webhook URL. Your workflow receives the method, headers, query, and body.

Events

Payload

methodstringRequired

HTTP method used for the delivery.

headersobjectRequired

Request headers. Shipfox keeps content-type, user-agent, x-delivery-id, x-request-id and replaces every other value with [redacted].

queryobjectRequired

Parsed query parameters. A repeated parameter becomes an array.

bodyany JSON valueRequired

Parsed JSON, form data, or plain-text body.

Was this page helpful?
Edit this page on GitHub

Setup

Create a webhook, inspect a test delivery, and verify that it starts a workflow run.

GitHub integration

Connect GitHub repositories for project code, event triggers, and workflow tools.

On this page

Event catalogRequestsreceived