Overview
Use Make to capture Cents webhook events and pass them to other apps or data pipelines. Make’s visual interface makes it easy to route data, filter by event type, and transform JSON payloads.
Supported Events
customer_created
customer_updated
order_created
order_updated
1. Create a Webhook in Make
Log in to Make.
Click Create a new scenario.
From the module list, search for Webhooks.
Choose Custom webhook.
Click Add, name your webhook (for example cents_events), and click Save.
Copy the Webhook URL that Make generates.
Click Run once to wait for a sample event.
2. Send a Test Event from Cents
Use Postman or curl to send a test webhook payload to the Make URL.
curl -X POST <YOUR_MAKE_WEBHOOK_URL> \ -H "Content-Type: application/json" \ -d'{"action":"order_created","order":{"id":"ord_test"}}'
2. When Make receives the event, click OK to confirm the payload structure.
3. Share your Make webhook URL with your Cents CSM to enable live event delivery.
3. Understanding the Payload
Cents webhooks are sent as structured JSON objects.
Example
```json
{
"action": "order_updated",
"order": {
"id": "ord_001",
"status": "Completed",
"orderTotal": 35.00
},
"customer": {
"id": "cust_001",
"email": "[email protected]"
}
}
```
Within Make, you can access fields using:
Order ID → {{1.order.id}}
Status → {{1.order.status}}
Customer Email → {{1.customer.email}}
If nested arrays (like order.services) don’t parse automatically, use JSON > Parse JSON or an Iterator module to loop through each item.
4. Build Your Scenario
Add any additional modules to create your automation:
App | Example Use Case |
Google Sheets | Add a row for every new order. |
Slack | Send a notification to a staff channel. |
Notify a customer when an order is completed. | |
CRM | Update customer data with loyalty metrics. |
Use Routers or Filters to branch flows by action type (e.g., only run steps for order_created).
5. Test and Deploy
Run your scenario once while triggering a test event in Cents.
Confirm the data maps correctly across modules.
Turn the scenario ON to receive real-time events.
6. Troubleshooting
Issue | Resolution |
No data received | Ensure the scenario is running (Run once) during testing. |
Fields missing | Re-run a test event to re-detect schema fields. |
Duplicate runs | Add a filter or deduplication key (like event ID). |