// Documentation
Agents that follow your process. Author a workflow once, try it against its draft, publish it, and let triggers, chats and endpoints start governed sessions that stop for a person's decision wherever you say so.
archmax automation runs agentic workflows for an organization. It is a web app, an API and a
worker around the archmax harness, the runtime that executes a
workflow.yaml state machine as a governed session. The
harness decides every move and every tool call; archmax automation adds what a runtime leaves
to its host: who may act, where the authored files live, what starts a session, which
credentials a tool uses, and where a person steps in.
A member of an organization reaches the agents their groups give them a role on: every agent through a built-in group, or the ones a custom group names. An agent is a git repository of workflows, skills and a system prompt, with one or more environments. Each environment has a draft, which the editor and the design agent write, and a history of published versions, which production sessions run.
One file is the workflow
A workflow’s states, transitions, tool and skill governance and hooks live in one
workflow.yaml. The editor draws it as state cards and transitions, the design agent can
write it for you, and the harness enforces it in every turn. See
workflows and the editor.
Draft, publish, promote
Edits land in the environment’s draft, and a testing session runs the draft as it stands. Publishing makes a version; a production session pins the version it opened on, and a promote carries a child environment’s published version into its parent. See agents and environments.
A person decides where it matters
A human state parks the session and raises a decision. It waits on the Sessions page under Needs you until a member holds one of its transitions for three seconds, with an optional note to the agent. See sessions and decisions.
Started from anywhere
Tools through connections
Tools come from collections: Activepieces pieces, remote MCP servers and the platform’s own services. A connection holds the credential, and each state allows or forbids the tools it may call. See connections and tools.
Cases before you publish
Cases drive a workflow through its states with tool mocks and grades, and an evaluation records running them in an environment. See evaluations.