Make.com Integration

What it does

There's no native Jitterflow app in Make's app directory yet. You don't need one — Make ships a built-in HTTP module that can make a request to any URL, and Jitterflow ingests over a plain HTTP POST. Point that module at your Jitterflow ingest URL instead of the final destination, and every event a scenario sends gets jittered delivery, retry with backoff, and a hosted dead-letter queue — the same handling described on how Jitterflow works.

How to connect

1. In your scenario, add a module and search for HTTP, then choose Make a request.
2. Set the URL to your endpoint's ingest URL from the dashboard (Endpoints → your endpoint → Ingest URL), Method to POST, and Body type to JSON.
3. Map whatever fields the previous module provides into the request body.

For repeat-run safety, add an idempotencyKey field to the body (see sending webhooks) so a scenario that retries after a timeout doesn't double-send.

Example scenario

New Shopify order → Jitterflow → ERP webhook. Trigger on Shopify's Watch Orders module, then an HTTP module sends the order payload to your Jitterflow ingest URL. Jitterflow spreads the resulting burst across a computed jitter window before forwarding to your ERP, so a flash-sale spike doesn't trip the ERP's own rate limiter.

Why route through Jitterflow

Make fires each scenario run as soon as its trigger fires — it has no awareness of your destination's rate limit and no dead-letter queue of its own beyond a manual re-run of a failed execution. Routing the outbound module through Jitterflow adds jitter, retry with backoff, per-destination isolation, and a DLQ with replay for anything that still fails, without changing anything else about the scenario.