> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/contribute/where-to-get-help.md).

# Where to get help

## Where to get help <a href="#where-to-get-help" id="where-to-get-help"></a>

n8n provides different support options depending on your plan and the nature of your problem.

### n8n community forum <a href="#n8n-community-forum" id="n8n-community-forum"></a>

n8n provides free community support for all n8n users through the [forum](https://community.n8n.io/).

This is the best source for answers of all kinds, as both the n8n support team and community members can help.

### Email support <a href="#email-support" id="email-support"></a>

n8n offers email support through the <help@n8n.io> for the following plans:

* [Enterprise plans](https://n8n.io/enterprise/) can use email support with an SLA for technical, account, billing, and other inquiries.
* Other [Cloud plans](https://n8n.io/pricing/) can use email support for admin and billing issues. For technical support, please refer to the forum.

## What to include in your message <a href="#what-to-include-in-your-message" id="what-to-include-in-your-message"></a>

When posting to the forum or emailing customer support, you'll get help faster if you provide details in your first message about your n8n instance and the issue you're experiencing.

### Your n8n instance details <a href="#your-n8n-instance-details" id="your-n8n-instance-details"></a>

To collect basic information about your n8n instance:

1. Open the left-side panel.
2. Select **Help**.
3. Select **About n8n**.
4. The **About n8n** modal opens to display your current information.
5. Select **Copy debug information** to copy your information.
6. Include this information in your forum post or support email.

### Details about your problem <a href="#details-about-your-problem" id="details-about-your-problem"></a>

To help resolve your issues more efficiently, here are some things you can include to provide more context:

* 🎥 **Screenshots or video recordings**: A quick Loom or screen recording that shows what's happening.
* 📚 **Relevant documentation**: If you've followed any guides or documentation, include links to them in your message.
* ☁️ **n8n Cloud workspace (if possible)**: If contacting support, provide the workspace URL for your n8n Cloud instance. It looks something like `https://xxxxx.n8n.app.cloud`.
* 📝 **Steps to reproduce the issue**: A simple step-by-step outline of what you did before encountering the issue.
* 📂 **Workflow or Configuration files**: Sharing relevant workflows or configuration files can be a huge help.

It may also be helpful to include a [HAR (HTTP Archive) file](https://en.wikipedia.org/wiki/HAR_\(file_format\)) in your message. You can learn how to generate a HAR file in your browser and how to redact sensitive details before posting using the [Har Analizer](https://toolbox.googleapps.com/apps/har_analyzer/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/contribute/where-to-get-help.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.