Do you need a webhook at all?
Webhooks in plain words
An app can learn what happened in another in two ways. It can keep asking "anything new?" on a timer, which is polling. Or the other app tells it the moment something happens, by posting a message to an address. That message is a webhook.
| Compared | Polling | Webhook |
|---|---|---|
| Who starts it | Your tool, on a timer | The other app, on an event |
| Speed | Often 1 to 15 minutes | Seconds |
| Empty checks | Some tools count them | None |
Inside is a small block of text, usually JSON: the event type, an event ID, the time, and the record. Your automation tool shows the fields as a list, so you never read the JSON.
How to set up a webhook, step by step
Step 1: Look for a built-in trigger first
If your tool already has "new payment" or "new order" for the app, use it. You only need your own address for apps and forms the tool does not know.
Step 2: Get an address from your tool
Create an automation that starts when called. It gives you a web address; keep it private, because anyone who has it can post to it.
Do this step in 50agents
Set up an automation that starts when my website form posts to it, and adds each submission as a row to my Enquiries sheet
Build itCaptain sets up an automation that starts when your form posts to its address, and adds each submission as a row to your own sheet without asking.
Step 3: Paste it into the sending app
In the app's webhook settings, paste the exact address and pick only the events you need. A redirect counts as a failure at Stripe, so use the address as given.
Step 4: Send a test and map the fields
Trigger one real event, then pick fields from the message for your steps. Stripe sends amounts in cents, so divide by 100.
Step 5: Skip repeats by ID
Senders retry when your address does not answer fast enough: Stripe for up to 3 days, Shopify up to 8 times over 4 hours. Keep the event ID and skip ones you have done.
Watch out. Events can arrive out of order too: "refunded" before "paid". Look the record up when the order matters.
Step 6: Check it is still firing
After repeated failures, Shopify removes the webhook. If events stop, open the sending app's webhook page, and read any missed records once by hand.
What can go wrong
Duplicate rows or emails
A retry ran your steps twice. Skip IDs you have already handled.
A slow step causes retries
Your address took too long to answer, so the sender tried again. Tools built for webhooks answer at once and do the work after.
A fake message
An address on the internet can receive anything. Real senders sign each message, and good tools check the signature on built-in triggers.
Test events mixed with real ones
Test mode and live mode send to the same address if you let them. Use separate addresses or check the mode field.
Questions people ask
What is the difference between a webhook and an API?
With an API, your tool asks the app for data. With a webhook, the app sends data to your tool when something happens. Most integrations use both.
Are webhooks secure?
They can be: the sender signs each message, and the receiver checks the signature. A webhook address with no signature check will accept anything, so keep it private.
Do I need a developer to use webhooks?
Not with automation tools: they create and check the address for you. You need one if you are building your own endpoint.
Why did I get the same event twice?
Senders retry when your address does not answer fast enough: Stripe for up to 3 days, Shopify up to 8 times over 4 hours. Keep the event ID and skip ones you have done.
How do I know a webhook stopped firing?
Check it is still firing: look at the sender's delivery log, or set an alert when no event arrives for a day you expect one. After repeated failures, Shopify removes the webhook.
Is a webhook faster than polling?
Yes. A webhook arrives within seconds of the event. Polling asks on a timer, often every 1 to 15 minutes, and some tools count the empty checks.