N8n Automation Configuration Issue
n8n automation configuration issues in 2026 most often come from three sources: environment variables not set correctly on self-hosted instances (missing `N8N_HOST`, `WEBHOOK_URL`, or `DB_*` variables), node settings that reference hardcoded IDs that changed (a HubSpot pipeline ID, a Slack channel ID), or a workflow that was exported from one environment and imported into another without updating credentials and resource IDs.
Why This Happens
- Configuration gaps between tools or services
- Missing integrations or manual workarounds that weren't designed to scale
- Changes in vendor behavior, pricing, or API that weren't communicated clearly
What To Check First
- Verify your current setup matches the vendor's latest documentation
- Look for recent changes — platform updates, new team members, configuration drift
- Check if the problem is consistent or intermittent (different root causes, different fixes)
When To Escalate
- The problem is costing you money or customers per week
- You've spent more than 2 hours on it without progress
- A vendor quoted you more than $500 and you're not sure if it's necessary
Dealing with this right now?
For self-hosted n8n: run `n8n start --help` to see all available environment variables, and compare against what you have set in your `.env` file or systemd service configuration. The most critical for webhooks: `WEBHOOK_URL` must be set to your public-facing URL, not `localhost`. For workflow portability: after importing a workflow, go through each node systematically and re-select the credential and any resource IDs (these are environment-specific and do not transfer between instances).
