> For the complete documentation index, see [llms.txt](https://handbook.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.n8n.io/start-here/about-the-automation-team.md).

# About the automation team

![](https://1295977995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FikYvt5xWzvK7NtuHBUPD%2Fuploads%2Fgit-blob-54b8de632775772ca6385c5902ef20ac3f86e010%2Fabout-the-automation-team-editorial.png?alt=media)

## Who we are

The Automation team exists to make n8n both more automated and better at building. We started by clearing manual work across the company, and our role has expanded well past that. Today it spans architecture, standards, enablement, governance, and the long-term reliability of everything that gets built, whether we build it ourselves or someone else does. Source: Automation team role Source: Automation team vision

## How we are structured

As of October 2026, we are eight people. We operate as a centralized internal team within Operations > Internal AI & Automation. We are not divided into permanent teams for Sales, Marketing, Support, People, Finance, Legal, Product, or Engineering. Instead, individuals or small groups partner with those functions according to the problem, capacity and required skills.

Our structure is intentionally multidisciplinary. This helps us prioritise high-impact company initiatives while also building standards and reusable infrastructure for other builders.

## Our values

### Take responsibility

We treat projects as ours, not just as tickets. We see them through from the problem to measurable impact, then help the people we worked with take ownership of what we built together.

### Be transparent

We share what we learn with each other, the company, and, when appropriate, the wider world. We write decisions and lessons down so others can understand, reuse, and improve them.

### Show kindness while remaining direct

We communicate honestly and clearly. We give and receive actionable feedback with respect and specificity.

### Stay curious

We stay curious about AI, automation trends, and better ways to solve problems. We experiment, ask questions, and share what we learn. These values shape how we deliver work, collaborate with partners, and help others build.


---

# 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://handbook.n8n.io/start-here/about-the-automation-team.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.
