> 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/how-we-build/how-we-build/automation-lifecycle/automation-intake-process.md). # Automation intake process ![](https://1295977995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FikYvt5xWzvK7NtuHBUPD%2Fuploads%2Fgit-blob-0148956d49b7f304a373001d63e8a052f9f03a80%2Fautomation-intake-process-editorial.png?alt=media) This page explains how requests enter the Automation team's queue and what people can expect before work begins. ## Why we use a shared intake A shared intake helps us focus on business-critical work that is properly scoped, likely to be adopted, and tied to a real outcome. It also makes our priorities and decisions visible to the wider organization. Intake starts with the problem rather than a proposed solution. This gives the Automation team enough context to decide whether to build, partner, enable the requesting team, or ask for more discovery. ## What we prioritize We assess each request across five dimensions: 1. **Business impact.** How much time, friction, cost, or risk could the work remove? 2. **Strategic alignment.** Does it support an active company or team priority? 3. **Process readiness.** Is the underlying process stable, documented, and understood well enough to automate? 4. **Durability.** Is the need likely to remain relevant long enough to justify the work? 5. **Adoption likelihood.** Is there a committed owner and a realistic plan for using the result? People do not need every answer before starting intake. The guided conversation helps expose missing context and the work needed before a request is ready to build. ## How the intake works 1. **Start a conversation.** At n8n, people use a guided conversation in Slack instead of a static form. It asks about the problem, the current process, and post-launch ownership. 2. **Review and prioritize.** The Automation team reviews every submission for business impact and process readiness. 3. **Follow up.** The team explains the next step or identifies what is missing, such as a process map or a named owner. 4. **Share priorities.** The team publishes what it has prioritized and explains why. 5. **Confirm ownership.** Every automation needs a person accountable for its use and the business process after launch. ## How AI supports intake AI powers the guided intake conversation, but it does not make the final prioritization decision. A member of the Automation team reviews every submission. People must not include passwords, credentials, or highly sensitive personal data. They should provide enough process context for the team to evaluate the request. ## What happens after submission The request enters the [prioritization stage](/how-we-build/how-we-build/automation-lifecycle.md#prioritization). The team reviews its value, readiness, dependencies, uncertainty, and likely adoption before deciding what to take on. --- # 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/how-we-build/how-we-build/automation-lifecycle/automation-intake-process.md?ask=&goal= ``` `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.