n8n Support

What is it?

n8n.io/support routes you to the right help channel for your situation. Free and self-hosted users get community support through the forum and GitHub issues. Paid Cloud plans add email support from the n8n team for instance, billing and account problems. Enterprise plans add SLA-backed response times, a dedicated contact, onboarding assistance and architecture review. The page also handles security disclosure and billing enquiries separately, because neither belongs in a public thread.

Triage: which channel for which problem

Support requests fail for one of two reasons: they were sent to the wrong place, or they arrived without enough information to act on. Triage first, then prepare, then send.

• 'My workflow does not do what I expect' → community forum.
• 'n8n itself behaves incorrectly and I can reproduce it' → GitHub issue.
• 'My Cloud instance is down / I was billed twice' → Cloud support.
• 'We need help designing for 100k executions a day' → Enterprise / consulting.
• 'I found a way to bypass authentication' → private security disclosure.

What to collect before you contact anyone

Every channel asks for roughly the same evidence. Gathering it once takes ten minutes and typically removes an entire round trip of clarifying questions.

• n8n version, and whether it is Cloud, Docker, npm or Kubernetes.
• For self-hosted: relevant environment variables (redacted) and reverse-proxy setup.
• Exact error text, copied as text — plus the execution ID on Cloud.
• A minimal reproduction workflow of two to four nodes.
• What changed recently: an upgrade, a credential rotation, a new integration.
• What you already tried, and the docs page you followed.

Escalating properly

If a business-critical process is down, do not wait politely on a free channel. Check whether your plan includes support with a response-time commitment, and use it — that is precisely what you are paying for.

When escalating, state business impact in one line: what is broken, how many people or customers it affects, and since when. Support teams triage by impact, and an impact statement moves you up the queue far more than urgency adjectives.

• Lead with impact: 'Order-sync workflow down since 09:00; 400 orders unprocessed.'
• Attach the execution ID and timestamps in UTC.
• Say clearly whether you have a workaround in place.
• Give one contact person, not a mailing list.

Reducing how often you need support at all

Most support tickets are preventable and trace back to the same handful of operational gaps. Closing them costs an afternoon and saves months of interruptions.

• Set up an error workflow that alerts on every failed execution.
• Pin the n8n version in your Docker image; never run :latest in production.
• Back up the database and the encryption key, and test the restore.
• Keep a staging instance and promote workflows through it.
• Log credential expiry dates — expired OAuth tokens are a top cause of sudden failures.

Support channels compared

How to use it — step by step

1. 1Classify the problem: workflow question, product bug, account issue, or security report.
2. 2Collect version, hosting type, exact error, execution ID and a minimal reproduction.
3. 3Remove every credential, token, internal URL and customer record from what you are about to share.
4. 4Open n8n.io/support and pick the matching channel.
5. 5Write one line of business impact at the top if the issue is production-affecting.
6. 6If it is urgent and business-critical, check whether your plan includes an SLA rather than waiting on the forum.
7. 7Once resolved, write down the root cause and add monitoring so the same failure alerts you next time.

Quick checklist

• Correct channel identified
• Version and hosting type recorded
• Exact error copied as text
• Minimal reproduction prepared
• All secrets and PII redacted
• Business impact stated in one line
• Workaround status made clear
• Root cause documented after resolution

Pro tips

• A two-to-three node reproduction gets answered far faster than a forty-node production workflow.
• Include what you already tried and which docs page you followed; it doubles the quality of the first reply.
• Keep an incident log — recurring failures usually share one root cause you can fix permanently.