The webhook builder
Point any platform at the app: choose the method, add your own headers, and write the JSON body it expects.
Last updated July 27, 2026
The webhook is how you connect something we have not built a card for. Rather than sending our shape and leaving you to translate it, you control the whole request - so an endpoint that expects its own contract can be fed without anyone writing a connector for it.
What you control
- Method - POST or PUT, whichever the receiving service expects.
- Headers - your own, including an Authorization header or an API key. Values are stored securely and shown masked once saved.
- Body - a JSON template with placeholders, or leave it empty to send our default payload.
- Signing secret - optional. When set, the body is signed so the receiver can verify the request really came from us.
The body template
Write the JSON the other service wants and drop placeholders where the values go - for example the email, the product, the variant. Substitution is escaped, so an apostrophe in a product title cannot break your JSON, and the template is checked when you save: an invalid one is refused there rather than failing silently every time it fires.
Test it before you rely on it
Send test sends one realistic request, with your method, your headers and your template, and shows you exactly what came back - status and response body. That is the difference between “saved” and “working”.
If it fails
A failed delivery is retried automatically, twice, with a short pause between. A request that is refused outright - a bad URL, a rejected key - is not retried into oblivion; it stops and is recorded so you can see it rather than wonder.