> ## Documentation Index
> Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Agents

> Set up agents that run on a schedule or when the month is ready to close, read your Control data, and post results to Slack after approval.

An agent is a workflow that Control runs for you: for example a P\&L summary posted to your finance channel every Monday, a daily cash digest, or a management report as soon as the month is ready to close. Control runs agents on its own servers, so nobody needs to keep a browser or the chat open.

Agents are enabled per workspace. If you don't see [**Agents**](https://app.control.dev/agents) (Agents) in the sidebar, ask Control to enable them for your workspace. Organization Owners and Admins create and publish agents; members can see them.

## What an agent does

Each agent has:

* **Instructions**: what to do on every run, written in plain language, such as "Summarize last week's P\&L against the week before and post it to #finance."
* **Tools**: the Control data it may read (statements, cash flow, transactions, budgets, invoices) and, optionally, Slack or Gmail.
* **Triggers**: when it runs. An agent runs on a schedule (for example every Monday at 08:00 in your time zone), when the previous month is closed in your accounting sources and its reporting data is ready, or when someone starts it from Agents.

An agent reads the same data you see in Control. It reports and prepares changes; it never changes accounting data, budgets or a connected system on its own.

## Set up an agent from the chat

Ask the chat for what you want, for example:

* "Send a P\&L summary to #finance every Monday morning."
* "Every weekday at 7, post yesterday's cash position to Slack."
* "When the books close, write a management report."

The chat checks what your workspace has connected, writes the agent's instructions, and shows one confirmation card with when the agent runs, what it reads, and where it posts. When you confirm, Control creates and publishes the agent. You can review or change it afterwards in [**Agents**](https://app.control.dev/agents) (Agents).

The chat also changes and runs the agents you have: "Move the weekly P\&L agent to 9:00", "Pause the crypto agent", "Run the month-end checker now" or "What did it find last time?". Each change is one confirmation card that shows the agent before and after.

A schedule runs at most once an hour: every run is a full agent run that counts against your workspace's AI allowance.

An agent reads Control's figures (statements, cash flow, transactions, invoices, budgets) and, when HubSpot is connected to Control, its deals and line items, for example "Every Monday, post the deals expected to close this month to #sales". From payroll it reads pay dates with the number of payslips and employees, but never an individual's salary.

## Custom connectors and skills

An agent can use your workspace's own connectors (external sources: MCP servers an Owner or Admin connected in Settings) and its skills.

* **Reading**: an agent calls the connector tools an Owner or Admin reviewed as read-only, for example to read open deals from your CRM.
* **Changing data**: an Owner or Admin can allow a connector tool as a write, for example HubSpot's tool that updates a company. An agent such as "When the month closes, update each customer's ACV in HubSpot" then proposes each change, and nothing changes until an Owner or Admin approves it in **Agents**. The change runs as the person who approves it, and Control cannot undo it.
* **Skills**: an agent can follow a workspace skill from Settings, Chat skills, such as how your team calculates ACV. It reads the skill's current text on every run. Personal skills stay in their owner's chats.

## Slack and Gmail

To post to Slack or draft emails, an Owner or Admin first connects Slack or Gmail in **Agents**. The agent can then post only to the channels, or draft only to the recipients, chosen when it was set up.

> [!NOTE]
>
> Every Slack message and Gmail draft an agent prepares waits for an Owner or Admin to approve it in **Agents**. Nothing
> is posted or sent before that. Gmail messages are created as drafts and are never sent automatically.

### Posting without approval

Some alerts cannot wait for approval. Where Control has turned this on for your workspace, an Owner or Admin can set an agent's Slack messages to **Post without approval** in **Agents**. The agent then posts to its chosen channels as it runs. Every post is still listed in **Approvals**. Limits:

* An agent posts at most 48 messages a day this way; more wait for approval.
* Only through the workspace's Slack connection, never a personal one.
* Only for an agent that reads figures and your workspace's setup, such as statements, cash flow, budgets and close readiness. An agent that reads transactions, counterparties, invoices, deals, documents, email or Slack messages cannot have it, because text people outside your workspace wrote could be posted unchecked. Nor can an agent that starts on an integration event, which another system sends.
* The chat never sets it: it creates agents whose messages wait for approval.

### Knowing what waits

The **Agents** item in the sidebar shows how many Slack messages, email drafts and proposed changes wait for an Owner or Admin. When an agent run ends with something waiting, Control also emails the workspace's Owners and Admins, at most once every 12 hours per agent. The email names the agent and how many items wait, never their content, and links to **Approvals** in **Agents**. Each Owner or Admin can turn these emails off there.

## Run history

Each run is listed on the agent in **Agents** with its status and result, and messages waiting for approval are listed there too. Without Slack, an agent's results are kept in Agents.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.