Agents

An agent gives an AI Agent node an identity of its own. Without one, the tools an AI Agent node calls run as the workflow. With one:

• the agent can only call the tools you allow (a node type and the operations of it), using only the connections you allow;
• it acts for a person only while that person has granted it the right to, and the grant ends on a date the person chose;
• every tool call is recorded in the activity log under both the agent and the person it acted for.

Agents live in the workflow module's Settings screen (/workflows/settings), on the Agents tab. See Settings.

Create an agent

1. Open Settings → Agents and click New agent.
2. Enter a Name (unique in the workspace) and, optionally, a Description.
3. Under Tools the agent may call, add one row per node type, for example store/slack, and list the operations it may call, separated by commas, for example postMessage, listChannels. Leave the operations empty to allow every operation of that node type. The agent can call nothing that is not listed.
4. Under Connections the agent's tools may use, tick the connections. A tool that runs with any other connection is refused.
5. Turn on Every tool call waits for a person's approval if every call should stop for a reviewer, whatever the node itself says. The approval works the same way as an AI Agent node's own tool approval (see Approvals).
6. Click Save agent.

Turning Active off disables the agent: its AI Agent nodes are offered no tools and every tool call is refused until it is turned on again.

Use an agent in a workflow

Open an AI Agent node and choose the agent under Agent identity. When you save the workflow, FluidGrids checks every tool wired to the node's Tool and Retriever ports: a tool the agent does not allow, a connection outside its connections, or an agent that is disabled or deleted is refused with a message naming the node.

While the workflow runs, the same checks are made again before every tool call, so narrowing an agent's tools takes effect on the next call even for workflows that were saved earlier. The model is only offered the tools the agent allows.

Let an agent act for you

An agent acts for the person a run is attributed to: whoever started it, or, for a scheduled, webhook or event run, the owner of the trigger that started it. That person must have granted the agent:

1. On the agent's card in Settings → Agents, enter how many days the grant should last (30 by default, at most 365) and click Grant.
2. The card then reads This agent may act for you until the end date.

A run that nobody holding a grant is attributed to cannot call the agent's tools: each tool call is refused with GRANT_REQUIRED, and the model is told the tool is unavailable. Scheduled and webhook-triggered workflows therefore need a standing grant from the trigger's owner.

Any member who may build workflows can grant an agent for themselves. A grant is always for the person giving it; nobody can grant on someone else's behalf.

Withdraw or revoke a grant

• Withdraw my grant on the agent's card ends your grant at once. The agent's next tool call for you is refused.
• Workspace admins see every grant on the card and can Revoke someone else's.
• Deleting an agent retires its identity and ends every grant.

If someone gives an agent more access — a new tool, operation or connection, or no longer requiring approval — every grant except theirs is withdrawn. A grant only ever covers what the agent could do when it was given; grant again after reviewing the change.

What is recorded

Each tool call an agent makes is recorded in the workspace activity log as agent.tool.called, with the agent as the actor (actor type app) and the person it acted for as on behalf of, together with the run, the node, the tool's node type and operation, whether it succeeded and how long it took. A refused call is recorded as agent.policy.blocked with the reason.

Reason	Meaning
TOOL_NOT_ALLOWED	The tool's node type or operation is not in the agent's list.
CONNECTION_OUT_OF_SCOPE	The tool runs with a connection the agent may not use.
GRANT_REQUIRED	The person the run is attributed to has no live grant for this agent.
AGENT_UNAVAILABLE	The agent is disabled or was deleted.
TOOL_NOT_WIRED	The tool is not connected to this AI Agent node.

Who can do what

Action	Default roles
See agents and their grants	Every FluidGrids role except Integration Engineer
Create and edit agents, grant an agent for yourself	Automation Owner, Automation Lead, Workflow Designer
Delete agents, revoke someone else's grant	Automation Owner, Automation Lead
Withdraw your own grant	Anyone who granted

See Roles and Permissions.