Add an Agent action when the workflow needs conversational AI to interact with an employee, for example, to ask questions, explain next steps, collect missing information, or use approved tools during the conversation.
An Agent action uses AI reasoning within the instructions and tools you configure. It isn't the same as a Run Tool action, which calls one integration directly without conversation.
Before you begin
Make sure you have:
- A workflow open in the designer.
- A configured Start action.
- Clear instructions for what the agent should accomplish at this step.
- Any tools the agent needs already created, tested, and set to Active in Agent Tools.
When to use an Agent action
Use an Agent action when the workflow needs to:
- Ask follow-up questions.
- Confirm details with the employee.
- Explain progress or next steps.
- Collect structured information for later actions.
- Optionally use attached Active tools during the conversation.
Add an Agent action
- Open the workflow in the workflow designer.
- From the Actions palette, add an Agent action.
- Connect it to the previous action, often Start or another completed step.
- Select the Agent action to open the node editor.
-
Enter a clear Name.
Example:
Time off assistant - Write Instructions that tell the agent:
- What to collect or explain.
- What to confirm before continuing.
- What structured outputs to return when finished.
- Under Tools, attach only the Active tools this agent is allowed to use at this step.
- Under Output fields, define the values later actions need.
- If the workflow uses progress milestones, set Workflow Step to continue the current step or start a new step label.
Example instructions
| Ask the employee to confirm the start and end dates and the leave type. Optionally collect a reason. Summarize the request before proceeding. When confirmed, return structured output containing the dates, reason, and leave type. |
Example output fields
| Name | Notes |
| startDate | Required for submit |
| endDate | Required for submit |
| leaveType | Required for most leave tools |
| reason | Optional unless your tool requires it |
Attach tools to the Agent action
Tools must be:
- Created and refined in Agent Tools.
- Set to Active.
- Attached to this Agent action.
An Active tool is still unavailable to the agent if it isn't attached to the Agent action.
Attach tools the agent may need to decide when to use during the conversation, such as checking leave balance or searching knowledge.
For the full step-by-step guide for using tools in workflows, see Use tools in workflows.
How Agent actions use knowledge and tools
- Knowledge: If a knowledge tool is attached and configured, the agent can use approved organizational knowledge.
- Tools: The agent can call only attached, Active tools.
- Boundaries: Instructions guide behavior, but permissions and available tools still limit what the agent can do.
What to do next
- Map Agent outputs into a Run Tool action when the next step is a system call.
- Add another Agent action later in the flow to confirm results to the employee.
- Publish and test the workflow.