The difference
You give an agent a message. It reads it, picks its tools, and may take a different path each time, even for the same question. That suits questions and open-ended work, where the right next step depends on what the agent finds. You give a workflow the inputs its form asks for. It then runs its steps in order: ask a model, call a tool, run code, check a value, wait for a person. The steps and the rules between them are fixed. What a model writes inside a step can still vary from run to run.Approvals
An Approval step pauses a workflow run until a person decides. The request appears in the approver’s Inbox, with the step’s prompt when the step sets one. By default the person who started the run cannot approve it, admins included, so someone else has to decide. The workflow’s builder can turn on Allow self-approval (governance exception). A request waits 24 hours by default, and if nobody decides in time it is rejected by default.- Enterprise, and a Business organization on SaaS: the approver is someone else who matches the step’s approver role or groups, or anyone who can see the workflow when the step names neither.
- SaaS personal account: you are the only person on the account, so you can decide an approval only when the step allows self-approval.
When to choose which
Choose an agent when:- people ask questions in their own words;
- the work changes from case to case, and the agent has to work out what to look up;
- a conversation is the natural way to work, with follow-up questions.
- the process must run the same way every time;
- a person must approve a step before the run goes on;
- you need a record of each step to review later.
An example
Answering staff questions about expense rules suits an agent: every question is different, and it searches the expense policy for each one. Paying out an expense claim suits a workflow: check the amount against the policy limit, ask a manager to approve anything above it, then create the payment entry. The steps never change, and the approval must happen before the payment.Using both together
- A workflow can run an agent inside one of its steps (an Agent Task step), with a set task, its model, the tools it may use and a time limit.
- An agent can run published workflows, added in its Workflows section. When a request matches one, the agent starts that workflow and tells you when the run waits for an approval. In Tasks, such a run shows Agent · and the agent’s name under Started by.
Where you see this in the app
- Workforce › Agents and Workforce › Workflows. See Agents overview and Workflows overview.
- Inbox: approvals waiting for you. See Inbox.
- New task: the worker selector offers agents and workflows. See Starting a task.