Quickstart
Workspace, one connection, one agent, one ceiling. About twenty minutes, most of it waiting for a provider to authorise.
This is the shortest path from nothing to an agent doing one real job. It deliberately connects one system rather than all of them, and briefs one agent rather than a team, because the failure mode for every operations tool is a fortnight of configuration before anything is worth looking at.
Open a workspace
A workspace is the boundary everything else sits inside: connections, boards, agents and the people you invite. Most shops need exactly one. Open a second only when you genuinely run two businesses that should not see each other’s orders, because nothing is shared between them by design.
Connect wherever orders actually arrive
One system, not five. For most people that is a marketplace or a storefront. A provider is connected once to your account and a workspace then selects that connection, so a second workspace can reuse it without the credential being copied anywhere.
Brief one agent on one job
Pick something you repeat every week and could describe to a new starter in two sentences. Chasing late suppliers and flagging stock cover are where most people begin. Name it, write the brief, and choose which tools it may touch.
Set the ceiling and the queue
Two settings decide how much rope the agent has: the spending ceiling it works inside, which starts at nothing, and which of its actions come to a person before they go out. Raise the first slowly. See Limits and ceilings.
Leave it a week, then read the brief
After about a week there is enough to look at: what moved, what queued, and where the agent asked for help. That is the point at which adding a second agent is worth doing, and not before.
What you need before you start
- An account, and an email address you can receive at. Sign-up is its own flow and is not covered here.
- Administrator access to whichever system you are connecting first. A provider connection almost always needs someone who can authorise an application against the account.
- A rough idea of one repeated job. Not a specification — two sentences.
What is deliberately not in the quickstart
Voice, custom connectors, the developer API and multi-workspace setups are all real and all documented, and none of them belong in a first hour. They each assume you already know what a run looks like when it goes well and what it looks like when it does not.