> For the complete documentation index, see [llms.txt](https://docs.hexabot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hexabot.ai/introduction/features.md). # Features Hexabot is an self-hosted AI workflow automation platform. It combines visual workflow design, execution, and operations in one platform. Build conversational, manual, and scheduled agentic workflows. Then extend them with actions, bindings, memory, content, and channels. ### AI workflow automation capabilities Hexabot includes the features teams need to build, run, and improve AI-powered workflows: * **Visual workflow editor** — design AI workflows visually or refine YAML definitions. * **Actions and bindings** — connect tools, services, models, and reusable capabilities. * **Memory and AI** — retain context and add AI-powered automation where it improves results. * **Channels and inbox** — run conversational workflows across channels and manage interactions. * **Workflow runs** — inspect executions, debug issues, and improve workflow reliability. * **Content and localization** — manage structured content and multilingual workflow experiences. * **Users and roles** — control access for operators, admins, developers, and teams. ### Workflow-first design Hexabot is built around workflows. Each workflow defines its trigger, execution steps, and outcome. This makes Hexabot useful for AI assistants, customer support automation, internal tools, and recurring operations. Hexabot supports three workflow types: * **Conversational** — for assistants, support flows, and guided interactions * **Manual** — for tasks started on demand by a user or operator * **Scheduled** — for recurring jobs, checks, and background automations ### Visual AI workflow editor The visual workflow editor gives you a clear view of AI workflow logic. You can build workflow paths, configure steps, and review each branch. Advanced users can also work with the YAML workflow definition. * Design AI workflows with a clear visual structure. * Review branches, loops, and execution paths quickly. * Test and publish workflow changes safely. Learn more in [Workflow Editor](/workflow-editor.md). ### Actions and bindings Actions are the units of work inside a workflow. They can send messages, call services, transform data, or trigger follow-up steps. Bindings make tools, models, and service definitions reusable across workflows. * Connect workflows to your tools and systems. * Reuse models, memory, and service definitions. * Extend behavior with integrations and helpers. ### AI memory and context Memory helps AI workflows retain useful state across interactions and workflow runs. AI features help workflows understand input, generate output, and work with structured knowledge. Together, they make agentic automation more context-aware and adaptive. * Keep useful context available across interactions. * Add AI where it improves speed or accuracy. * Use memory to support better decisions and responses. Learn more in [Memory](/memory.md). ### Omnichannel workflows and inbox Hexabot runs conversational workflows where users already interact. You can connect channels, receive events, and manage customer conversations from a shared inbox. Human operators can step in when automation needs a handoff. * Support website and external channel experiences. * Track interactions from one inbox. * Hand off to human operators when needed. ### Workflow monitoring and operations Hexabot helps teams monitor AI workflow activity and troubleshoot automation issues. You can review workflow run history, inspect execution details, and follow failures to the exact step. This makes it easier to improve workflow reliability over time. * Track workflow activity and recent outcomes. * Inspect runs to debug failures or unexpected behavior. * Manage operations from the admin workspace. Learn more in [Workflow Runs](/workflow-runs.md). ### Workflow content and localization Hexabot includes workflow content tools for managing structured business knowledge. This keeps business knowledge accurate and reusable without changing workflow logic. Localization supports multilingual customer and agent experiences in the same workspace. * Store structured content in one place. * Reuse content across workflows and channels. * Manage languages and translations centrally. Learn more in [Content](/content.md) and [Localization](/localization.md). ### Role-based access control Hexabot supports team collaboration with role-based access control for workflow operations. You can invite team members, assign permissions, and separate responsibilities across operators, admins, and developers. * Add operators, admins, and collaborators. * Control access with roles and permissions. * Keep teams organized as your workspace grows. Learn more in [Users and Roles](/users-and-roles.md). ### Explore next * [Overview](/introduction/overview.md) * [Create your 1st workflow](/quickstart/create-your-1st-workflow.md) * [Workflow Editor](/workflow-editor.md) --- # 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.hexabot.ai/introduction/features.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.