Quick Answer
A typical n8n webhook workflow (Webhook → IF → Slack) migrates to Requex in about 10 minutes. There is no one-click importer — n8n and Requex use different graph formats — but this guide maps every common n8n node to its Requex equivalent.
Migrate from n8n to Requex.me
If your n8n workflows are all variations of "webhook comes in, do something, notify someone," migrating to Requex.me takes one afternoon. This guide walks the mapping node-by-node and covers the gotchas.
Before You Start
- Export your n8n workflow JSON — Workflows menu → "Download". You will reference the node configs, not import them.
- List your active webhook sources (Stripe, Shopify, GitHub, etc.). You will update each sender's URL after migration.
- Identify secrets used in each workflow (HMAC secrets, Slack tokens, HTTP auth). You will re-enter them in Requex.
- Create a Requex.me account and confirm your email.
Node-by-Node Mapping
| n8n Node | Requex Equivalent | Notes |
|---|---|---|
| Webhook (trigger) | Trigger | Single URL, always active |
| Schedule Trigger | Trigger (cron) | Use cron syntax, supports timezones |
| IF | Filter | Single condition drops non-matches |
| Switch | Switch | Direct equivalent |
| Set | Transform | JavaScript or JQ template |
| Code | Transform (JS) or JQ Transform | Same JS API surface |
| HTTP Request | HTTP Resilient | Built-in retry with backoff |
| Slack | Slack | Bot token or webhook URL |
| Discord | Discord | Webhook URL + template |
| Email Send | SMTP or built-in sender | |
| Google Sheets | Google Sheets | Service Account JSON auth |
| Split in Batches | Iterator | Iterates over array fields |
| Merge | Merge / Join | Merge combines streams, Join waits for both |
| Wait | Delay | Fixed or template duration |
| Error Trigger | Try/Catch | Wrap risky nodes inside |
| Crypto (HMAC) | Webhook Verify | No code required |
Expression Syntax
Both tools use double-brace expressions, but the variable names differ:
| n8n | Requex |
|---|---|
| {{ $json.body.id }} | {{body.id}} |
| {{ $json.query.foo }} | {{query.foo}} |
| {{ $json.headers["x-sig"] }} | {{headers.x-sig}} |
| {{ $json.method }} | {{method}} |
For deep transforms, Requex supports JavaScript in the Transform node (same API as n8n's Code node) or jq in the JQ Transform node.
Worked Example: Stripe → Slack
Here is a concrete migration of a common workflow:
In n8n
- Webhook node, POST, production URL copied to Stripe
- Code node verifying Stripe signature with crypto
- IF node:
{{ $json.body.type }}equalscharge.succeeded - Slack node with channel and message template
In Requex
- Create a webhook — copy the URL, leave it in Stripe's config
- Open Workflows, create a new workflow, pick your webhook as the trigger
- Drop a Webhook Verify node: pick HMAC-SHA256, paste the Stripe signing secret, point at the
stripe-signatureheader - Drop a Filter node: condition
{{body.type}}equalscharge.succeeded - Drop a Slack node: pick channel, template message with
{{body.data.object.amount}} - Save, and the workflow is live — no Active toggle needed
Total time: ~8 minutes. The Stripe signing secret is the same value you used in n8n.
Gotchas
Single URL vs dual URL
n8n has test and production URLs. Requex has one URL. Update your webhook sender once and it works in both "test" and "real" scenarios.
No "Activate" toggle
A Requex workflow is live as soon as you save it. If you need to pause a workflow, disable the trigger or add a top-level Filter that drops all events.
Credentials are per-node, not project-wide
n8n has a shared credentials store. Requex nodes store credentials inline. This makes it easier to have different Slack tokens per workflow but means you cannot reuse a credential across workflows (yet).
The $node scope does not exist
n8n lets you reference prior node output as {{ $node["Webhook"].json }}. Requex passes the payload forward — use {{body}} or add a Transform node to stash values.
Migration Checklist
- Export each n8n workflow JSON for reference
- Create a Requex webhook per source system
- Rebuild workflow on Requex canvas using the node mapping table above
- Paste all secrets (HMAC, API tokens) into the new nodes
- Send a test event to the Requex URL — confirm the Run Trace drawer shows each step succeeded
- Update the webhook sender in the external system (Stripe, Shopify, etc.) to point at the Requex URL
- Deactivate the n8n workflow (do not delete yet)
- Monitor for a few days, then retire the n8n setup
FAQ
Is there a one-click importer?
No. n8n's internal graph format uses very different node identifiers and expression syntax — an auto-importer would produce broken workflows. Manual migration takes 10–20 minutes per workflow and catches inconsistencies.
What if I use a node Requex does not have?
Use the HTTP Resilient node to call the service's API directly, or run custom logic in a Transform node. For niche SaaS-specific nodes (Airtable, HubSpot CRM), staying on n8n may be the right call.
Will my webhook sender notice downtime during migration?
No — run both in parallel. Point the sender at Requex, keep n8n Active temporarily, then deactivate n8n once you are confident.
How do I handle n8n credentials sharing?
Re-enter each secret in each Requex node that needs it. If you share a credential across many workflows, copy it from a password manager to keep the values identical.