Actions and connections

Give an agent actions in your apps, choose which account it runs on, and decide which actions ask for confirmation.

Actions are what an agent can do: search a mailbox, create a task, read a file. Connections are the accounts it uses to do that. You manage both in the Setup tab, in the Actions section.

Add actions

  1. Open the picker

    In Setup, under Actions, choose Add action. The Select action window opens.

  2. Find what you need

    Browse by category or use Search actions. The categories are Capabilities (built-in abilities such as web search, image generation, data analysis, canvas and memory), Apps (individual actions from your connected apps) and Subagents (other agents this agent can hand work to).

  3. Add it

    Choose Add next to an action. A capability can include several actions and shows what it contains.

If you attach no specific actions, the agent can use all standard actions. As soon as you attach specific ones, it uses only those. Some actions need a higher plan and show a Needs Business plan badge; runs on your current plan skip them.

If your instructions mention email, a calendar or a knowledge base but nothing matching is attached, a notice warns you and offers Add actions or Add knowledge.

Which account it runs on

Each app action shows an Account picker:

  • Automatic: the workspace's shared connection if there is one, otherwise your own.
  • A specific account, shown as organisation or personal.
  • Link another account to connect one more.

Use Connect, Reconnect or Disconnect next to an app, and Test to check that the connection works.

A personal connection only works for the person who made it. If someone else starts the agent, or a schedule runs it for someone else, actions that depend on that personal connection are skipped. For an agent that several people use, ask a workspace admin to connect the app for everyone with Connect for everyone. See Connect apps.

If a connection stopped working, the agent shows Reconnect needed. You can still start a run: the agent skips the actions whose apps are not connected and says which ones, with a Show in Actions link.

Ask first: confirmations per action

Every action has an Ask for approval switch, shown as Ask first on the action row.

  • The default depends on what the action can change: actions that change things in another app ask first, read-only actions do not.
  • Your choice for this agent overrides the default, and the row tells you which one applies.
  • Templates can come with approvals switched on that you cannot switch off.

When an action that asks first is reached during a run, the run pauses until someone approves. See Runs and approvals.

Reset standing approvals clears every Always allow and Allow this session the agent has collected in its runs. Future runs ask again until you grant them.

Some actions have their own settings, shown under Settings for this action. A setting that differs from the default is marked as changed.