2d (edited) • 📘 Tutorials & Guides
Managing variables across n8n workflows
The problem:
- Same workflow, different environments (test vs prod)
- Different API endpoints for each
- Hardcoded values = manual updates everywhere
- One typo = cascade of failures
My solution: Centralized config in Airtable.
How it works:
1. Store all variables in Airtable "Variables" table
- API endpoints
- Webhook URLs
- Feature flags
2. Automation script reads the table and:
- Normalizes variable names (MY_API_URL → myApiUrl)
- Switches environments (PRODUCTION=true strips "-test" suffix)
- Groups related configs (all NCA_* endpoints together)
- Sends clean payload to n8n webhook
3. n8n workflows receive structured config, no hardcoding
The win:
- Change one Airtable cell → all workflows update
- Toggle PRODUCTION flag → instant environment switch
- Add new variable → automatically available everywhere
No more:
- Hunt-and-replace across 50 workflows
- Which workflow still has the old endpoint?
Real example:
- N8N_WEBHOOK_URL in Airtable Variables table: "https://n8n.yourdomain.com/webhook-test/xxxxx"
- Set PRODUCTION=true
- Script auto-strips "-test"
- Once you flip the n8n workflow to production, Airtable trigger production webhook: "https://n8n.yourdomain.com/webhook/xxxxx"
Works with any n8n + Airtable setup.
Airtable base (with script included) → Template Library, look for the Airtable base link at the bottom of the page.
0
0 comments
Managing variables across n8n workflows
skool.com/build-automate
Own your automation. No execution limits, no vendor lock-in. Master n8n, Docker & production systems. Full control, predictable costs.
Leaderboard (30-day)
1
+4
2
+2
Powered by