Webhooks let Cents send customer and order updates to Zapier the moment they happen. Zapier can then add rows to a spreadsheet, send emails, update your CRM, or connect to thousands of other apps.
Use this if you want Cents events, like new customers or completed orders, to automatically trigger Zaps.
Before you start
You have a paid Zapier plan. Webhooks by Zapier isn't available on the Free plan.
You have Admin access to Cents Business Manager and can see Integrations > Webhooks. If you don't see Webhooks, text our Support team to turn it on.
You can create a test customer or test order in Cents. You'll need a real event to set things up.
How Cents webhooks work
Cents sends a message (a webhook) to your URL each time something happens: customer_created, customer_updated, customer_marketing_optin, order_created, order_updated, and order_completed.
Each message is JSON. The event field tells you which event it is, followed by order, customer, and service details. Some fields can be empty.
There's no "send test" button. To test, create or update a real (test) customer or order in Cents.
If your URL doesn't respond, Cents retries up to 5 times. After that, the event is not sent again.
You can see every send in Business Manager under the webhook's Event Log for 7 days.
Step 1: Create a Catch Hook in Zapier
In Zapier, click Create > Zaps.
For the trigger, choose Webhooks by Zapier, then the event Catch Hook, and click Continue.
On the Test tab, copy the webhook URL. It looks like https://hooks.zapier.com/hooks/catch/...
Step 2: Add the webhook in Business Manager
In Cents Business Manager, go to Integrations > Webhooks and click + Webhook.
Label (optional): a name for your reference, like "Zapier - completed orders".
Endpoint URL: paste the URL you copied from Zapier.
Authentication: leave it on None unless your Zapier setup requires a custom header.
Events to send: all events are checked by default. Uncheck everything this Zap doesn't need.
Click Save. For more on this screen, see How to Set Up and Use Webhooks in the Business Manager.
Step 3: Send a real event and test
In Cents, create or update a test customer or order that matches one of the events you picked.
Right after, go back to Zapier and click Test trigger. Pick the request that just came in.
Step 4: Build and publish your Zap
If you send more than one event to this URL, add a Filter step: event > (Text) Exactly matches > order_completed (or whichever event you want).
Add your action steps and map the Cents fields.
Click Publish to turn the Zap on.
Want Zapier to do things in Cents? Creating a customer or sending an SMS from a Zap uses the Cents Zapier app, which is separate from webhooks. Accept the Cents app invite, then add a Cents action step. Zapier asks you to log in to Cents when you add that step.
Troubleshooting
Don't see Webhooks under Integrations?
The feature isn't turned on for your account yet. Text our Support team and we'll enable it.
Can't find Webhooks by Zapier, or it's locked?
It requires a paid Zapier plan. Upgrade your plan in Zapier.
Test trigger says "No requests found"?
Zapier only sees events that arrive after the hook is created. Create or update a real test order or customer in Cents, then click Test trigger again right away.
The Event Log in Business Manager shows "Failed"?
Zapier didn't accept the event. Open it with View to see the response. Most often the Zap is off or the URL is wrong. Failed events are retried up to 5 times, then dropped.
The Zap ran during testing but nothing happens now?
Make sure you clicked Publish and the Zap is On. Zapier ignores events sent to Zaps that are off.
Zapier returns 404?
The Zap was turned off or deleted. Turn it back on, or rebuild it and paste the new URL into Business Manager. It can take a few hours for Zapier to start returning 404, so failures may appear late.
You transferred the Zap to someone else?
The webhook URL changes when a Zap changes owners. Copy the new URL and update it in Business Manager.
Fields are missing in Zapier?
Send a newer event and choose it in Test trigger. Some fields are legitimately empty, like a delivery window on a walk-in order.
Your filter never passes?
Filter on the event field. Older guides said "action", which no longer exists.
The Zap runs too often?
Every order status change sends order_updated. If you only need finished orders, use order_completed, or add a filter.
Getting duplicate runs?
Duplicates can happen. Add a filter or a Storage by Zapier step that checks event + order.id + order.updatedAt.
Got an email that your webhook endpoint was disabled?
Cents disables endpoints that keep failing. Fix the Zap, then edit or re-add the webhook in Business Manager.
Zapier keeps asking you to log in to Cents?
That only happens with Cents app action steps, not with webhooks. Accept the Cents app invite and connect your account once.
Video walkthrough
Note: This video shows an older setup where your account manager added the webhook URL for you. Today, you add it yourself in Integrations > Webhooks as described above.
Need assistance?
Feel free to text our Cents Support team at 888-302-8809.

