Frequently asked questions
The questions that come up before the first workflow, including the ones whose honest answer is no.
Workflows
- Can a team share a workflow?
No. A workflow has exactly one owner, who builds it, runs it and answers its approvals.
- Can I test a workflow without touching real systems?
A test run is a real run with real credentials and real side effects, and there is no separate staging environment.
- Do I need to know how to code to build a workflow?
No. You describe the process in an interview and correct the first real runs, and the platform writes the code.
- Is there a library of ready made workflows to start from?
No. Every workflow starts from a name and the interview, and there are no prebuilt templates in the product.
- What happens when a workflow breaks?
The failure opens a repair interview, and you choose between a checked patch and sending the workflow back to learning.
- What if the process is different depending on the case?
The steps run in the same order every time. Variation lives inside a step, and genuinely open judgement stays with an agent.
- When does a workflow start running on its own?
When you decide it is ready. No run count and no confidence score flips it for you.
Triggers and schedules
- What can start a workflow?
A schedule, an event from a system you connected, or a person pressing run.
Runs
- Can I see exactly what a run did?
Yes, and an autonomous run is recorded the same way a supervised one is.
- Can I stop a run that is already going?
Yes. You can cancel a live run from the screen you are on, and stop the whole workflow in the same action.
- Can I test a workflow without touching real systems?
A test run is a real run with real credentials and real side effects, and there is no separate staging environment.
- What does a single run cost?
It depends how much of the workflow is still agentic, and every run shows you its own number.
- What happens when a workflow breaks?
The failure opens a repair interview, and you choose between a checked patch and sending the workflow back to learning.
- When does a workflow start running on its own?
When you decide it is ready. No run count and no confidence score flips it for you.
- Will it do something irreversible without asking me?
An agent step is instructed to stop and ask before anything consequential, and a gate you pinned always stops. Only the second one is a guarantee.
Approvals
- Who gets asked when a run needs approval?
The workflow's owner, and only the owner. There are no approval chains, no escalation and no timeout.
- Will it do something irreversible without asking me?
An agent step is instructed to stop and ask before anything consequential, and a gate you pinned always stops. Only the second one is a guarantee.
Integrations
- Does it work with the tools we already use?
If the service has an API and you can give the workflow a credential for it, yes. There is no catalogue of supported apps.
Pricing
- Can I stop a workflow running up a large bill?
Yes. Set a monthly cap on one workflow or on everything you run, and unattended work parks instead of spending past it.
- What does a single run cost?
It depends how much of the workflow is still agentic, and every run shows you its own number.
Security
- Can a team share a workflow?
No. A workflow has exactly one owner, who builds it, runs it and answers its approvals.
- Can I stop a workflow running up a large bill?
Yes. Set a monthly cap on one workflow or on everything you run, and unattended work parks instead of spending past it.
- Who can see the data our workflows handle?
Each workflow runs in its own sandbox with only the credentials it declared, and it acts with its owner's access rather than a shared account.