You have a Make account.

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.

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.

In Make, create a new scenario.

Click the +, search for Webhooks, and choose Custom webhook.

Click Add, give the webhook a name (like "Cents orders"), and click Save.

Click Copy address to clipboard. The URL looks like https://hook.us1.make.com/... Copy this webhook address, not the URL in your browser bar.

Click Run once so Make starts listening.

In Cents Business Manager, go to Integrations > Webhooks and click + Webhook.

Label (optional): a name for your reference, like "Make - completed orders".

Endpoint URL: paste the URL you copied from Make.

Authentication: leave it on None unless your Make setup requires a custom header.

Events to send: all events are checked by default. Uncheck everything this scenario doesn't need.

Click Save. For more on this screen, see How to Set Up and Use Webhooks in the Business Manager.

In Cents, create or update a test customer or order that matches one of the events you picked.

Back in Make, the webhook module should show Successfully determined. Make now knows what Cents data looks like.

Add the modules you want after the webhook, like Google Sheets or Gmail, and map Cents fields into them (for example, {{1.order.orderCode}} or {{1.customer.firstName}}).

If you send more than one event to this webhook, add a Router or Filter on the event field so each path only runs for the right event.

Click Save, then switch the scenario ON. Keep scheduling set to Immediately.

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.
​

Make never shows "Successfully determined"?
Make only listens right after you click Run once. Click it again, then create or update a test order or customer in Cents. There's no test button in Cents, so a real event is needed.
​

Pasted the wrong URL?
The URL must start with https://hook. and come from the webhook module's Copy address button. The address in your browser bar won't work. Edit the webhook in Business Manager and paste the correct one.
​

The Event Log in Business Manager shows "Failed"?
Make didn't accept the event. Open the event with View to see the response, then check the fixes below. Failed events are retried up to 5 times, then dropped.
​

Make returns a 400 error?
Usually the webhook has a strict data structure that doesn't match the Cents payload, or several event types are going to one webhook. Remove the data structure in Make, or uncheck the extra events in Business Manager.
​

Make returns 410 Gone?
Make turns off webhooks that aren't attached to a scenario for more than 5 days. Create a new custom webhook and update the Endpoint URL in Business Manager.
​

Fields you expected are missing in Make?
Right-click the webhook module, choose Redetermine data structure (or Detect new values), and send another real event. Some fields are legitimately empty, like a delivery window on a walk-in order.
​

Your filter or router never matches?
Filter on the event field (for example, event equals order_completed). Older guides said "action", which no longer exists.
​

The scenario stopped running?
Make turns a scenario off after an error when it runs immediately. Fix the module that failed, switch the scenario back ON, and check its History.
​

Getting the same order more than once?
Duplicates can happen. Add a filter or a Make Data store check on event + order.id + order.updatedAt to skip repeats.
​

Too many runs from order updates?
Every status change sends order_updated. If you only care about finished orders, use order_completed instead.
​

Make says "Queue is full" or returns 429?
You've hit Make's plan limits. Add operations or credits in Make, or send fewer events to this webhook.
​

Got an email that your webhook endpoint was disabled?
Cents disables endpoints that keep failing. Fix the Make side, then edit or re-add the webhook in Business Manager.
​

Want to use one Make webhook for two scenarios?
A Make webhook can only belong to one scenario. Create a second webhook in Make and add it as a second webhook in Business Manager.