Integrate with Make

Overview

Make counts operations: each module run in a scenario uses at least one. When a webhook triggers a scenario for every event, operations add up quickly. With Webbu in front, a scenario run receives a batch of events instead of a single one.

Setup

1. Create a Make webhook

1. Create a scenario in Make
2. Add Webhooks → Custom webhook as the trigger and create a webhook
3. Copy its URL (e.g. https://hook.us1.make.com/abc123…)

2. Create a Webbu buffer

curl -X POST https://webbu.dev/api/v1/admin/buffers \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $WEBBU_API_KEY" \
  -d '{
    "bufferId": "b_make",
    "projectId": "p_automation",
    "name": "Make batch",
    "groupKey": { "mode": "jsonpath", "path": "$.customerId" },
    "batch": { "maxItems": 50, "maxBytes": 262144, "idleTimeoutMs": 10000, "maxWaitFromFirstMs": 60000 },
    "delivery": { "url": "https://hook.us1.make.com/abc123" }
  }'

$.customerId groups events by customer; use a field your events share.

3. Point your webhook source to Webbu

https://webbu.dev/api/v1/ingest/p_automation/b_make

Then send one test webhook through Webbu so Make can learn the batch structure ("Redetermine data structure" on the webhook module).

4. Process the batch

1. After the webhook trigger, add an Iterator over items
2. Map payload.* fields from each item into your modules
3. Or skip the iterator and act on the whole batch (e.g. one row or message per customer using webbu.groupKey and window.itemsCount)

The batch looks like:

{
  "webbu": { "bufferId": "b_make", "groupKey": "customer_123", "segment": 0, "…": "…" },
  "window": { "firstItemAt": 1767225600000, "lastActivityAt": 1767225620000, "itemsCount": 3 },
  "items": [
    { "messageId": "…", "receivedAt": 1767225600000, "payload": { "event": "order.created", "customerId": "customer_123", "orderId": "order_1" } },
    { "messageId": "…", "receivedAt": 1767225610000, "payload": { "event": "order.shipped", "customerId": "customer_123", "orderId": "order_1" } },
    { "messageId": "…", "receivedAt": 1767225620000, "payload": { "event": "order.delivered", "customerId": "customer_123", "orderId": "order_1" } }
  ]
}

How much you save

Without Webbu, every event runs the scenario. With batches, the trigger runs once per batch; modules after an iterator still run once per item. The biggest savings come from scenarios that handle the batch as a whole or filter items before the expensive modules.

Benefits

• Fewer scenario runs and operations
• All events of a customer or order in one run
• Retries and a dead letter queue when Make is unavailable