> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/integrations/n8n.md).

# n8n

Integrate Currents in n8n ecosystem

Use [n8n](https://n8n.io) to connect Currents with 1,300+ apps and automate workflows from your test results.

### How to access

1. In the dashboard, open your **Project** → **Settings** → **Integrations**.
2. Under **Available Integrations**, find the **n8n** card.
3. Click **View Documentation** to open the n8n integrations page filtered for Currents.

[n8n integrations – Currents](https://n8n.io/integrations/?q=currents)

### Integration requirements

The Currents n8n node requires a [Currents API Key](https://docs.currents.dev/api/get-started/authentication) to be included in n8n credentials.

### What can be done?

* Build workflows that react to Currents test runs and results.
* Connect Currents to Slack, email, CRMs, databases, and other tools via n8n nodes.
* Automate notifications, reporting, and triage without writing code.

No setup is required in the Currents dashboard beyond opening the link; configure your workflows in n8n.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/resources/integrations/n8n.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.