> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/workflow-builder.md). # Workflow Builder How to create custom automations/integrations directly in ION The **Workflow Builder** brings a full-featured, visual integration authoring experience directly into ION. From inside ION you can design, test, and iterate automation/integration workflows that connect ION data and processes to external systems — all without switching tools. The embedded builder provides a visual, low-code/no-code canvas for composing steps, transforming data, and handling errors so users can rapidly create repeatable integrations that automate work across your stack. ION’s workflow builder is surfaced in the product as a first-class page (similar to the Integrations / Marketplace link) and is available behind a feature flag while the integration is rolled out. Access is controlled by ION permissions so administrators can enable the workflow builder for the right users and teams. This tight embedding means you get the power of workflow tooling while staying inside ION’s workflow and security model. This manual contains step-by-step guidance for creating and publishing flows with the workflow builder in ION, plus notes on access, testing, and best practices to help your team get started quickly. --- # 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://manual.firstresonance.io/workflow-builder.md?ask=&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.