Requex.me LogoRequex.me

Deliver one event to multiple systems without racing: destinations run strictly in sequence, each with its own retry budget, after a dedup gate. Destination 2 never sees an event destination 1 rejected.

Ordered fan-out to three destinations

delivery5 steps·Free — clone into your account in one click
Use this template Browse all templates

How this workflow works

  1. 1. Source webhook

    trigger

    Starts the workflow — from an inbound HTTP request or on a schedule.

  2. 2. Dedup first

    webhook-dedup

    Stops the run if the same key was seen within the TTL. Providers deliver at-least-once — duplicates WILL happen.

  3. 3. Destination 1 (must succeed first)

    http-resilient

    HTTP request with retries, backoff, and jitter. ⚠ On success the response body replaces the payload.

  4. 4. Destination 2 (runs after 1)

    http-resilient

    HTTP request with retries, backoff, and jitter. ⚠ On success the response body replaces the payload.

  5. 5. Destination 3: notify

    discord

    Posts a message to a Discord channel via a channel webhook.

Run it without writing any code

Every step above is a visual node in the Requex workflow builder. Clone this template, fill in your own credentials where a step needs them, and it runs in the cloud — no server, no cron box, no npm install. Webhook-triggered workflows get an always-on URL; scheduled ones run on your cron expression.

Open this template in the builder