Connect Make (Integromat)

Make (formerly Integromat) is a workflow automation tool similar to Zapier, often used for more visual, multi-step scenarios. The webhook setup in Hilal Chatbot is identical — only the receiving end differs.

In this guide:

• Why pick Make over Zapier
• Create a Make scenario
• Register the webhook
• Test the delivery
• Build the rest of the scenario

Why Make

• Visual scenario builder — drag-and-drop multi-step flows with branching, error handling, and aggregation.
• Often cheaper at scale — Make’s pricing model favors many small operations.
• Webhooks-first — Make has had robust webhook support since launch.

If you already use Zapier, stick with Zapier. If you’re picking, evaluate both.

Step 1: Create a Make scenario

1. In Make, click Create a new scenario.
2. Add a module → search for Webhooks → Custom webhook.
3. Click Add to create a new webhook.
4. Make gives you a URL (e.g., https://hook.eu1.make.com/abcdef...). Copy it.

Step 2: Register in Hilal Chatbot

In Hilal Chatbot, Integrations → Webhooks → New webhook:

• URL — paste the Make hook URL.
• Events — pick what you want.
• Description — “Make — escalations to PagerDuty” or similar.

Screenshot: The Make scenario builder with a webhook trigger and follow-up modules.

Click Save.

Step 3: Test the delivery

In Hilal Chatbot, click Test on the webhook row. Make’s webhook module is now “listening” — it will capture the test payload and use it to define the data structure.

In Make, click Determine data structure. The captured payload becomes the schema.

Step 4: Build the rest of the scenario

Add follow-up modules in Make:

• Filter — only proceed if event_type == 'escalation.triggered'.
• Action — call PagerDuty’s API, send a Slack message, write to Airtable.
• Aggregator — combine multiple events.
• Error handler — retry, notify, fall back.

Test the scenario, save, turn it on.

Step 5: Verify deliveries

The same delivery log in Hilal Chatbot tracks Make webhook firings. Use it to monitor:

• Successful deliveries (Make scenario triggered).
• Failed deliveries (scenario broken — fix in Make).
• Retry attempts.

Multi-step scenarios that fan out

Make’s strength is fanning one Hilal Chatbot event into many actions:

• lead.captured → 1) save to Airtable, 2) create Salesforce record, 3) send welcome email, 4) notify Slack.

Build it once in Make instead of creating four separate Zaps.

Tips

• Use Make’s data store for stateful flows. Track conversation IDs, dedupe events, build aggregations across many calls.
• Set scenario error handlers. A bad token in a downstream API shouldn’t break your whole sync.
• Watch your operations budget. Make charges per operation; high-volume message.received subscriptions can drain quickly.

Troubleshooting

• Webhook fires but scenario doesn’t run. Scenario may be inactive or stuck on a paused step.
• “Bundle could not be processed.” Payload schema changed. Re-determine data structure in the webhook module.
• Operations exhausted. Reduce subscription scope or upgrade Make plan.

What’s next