Requex.me LogoRequex.me

Point providers at Requex instead of n8n directly. Every event is archived first, then forwarded to n8n with retries. If your n8n instance is down, you get a Slack alert and the payload waits safely for replay.

n8n safety net — never miss a webhook again

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

How this workflow works

  1. 1. Point your provider here

    trigger

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

  2. 2. Archive every event first

    requex-inbox

    Archives the current payload into one of your Requex webhooks.

  3. 3. Forward to n8n

    http-resilient

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

  4. 4. n8n unreachable

    slack

    Failure path — runs only when the previous step fails after retries.

    Posts a message to a Slack channel via an incoming 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