> ## Documentation Index
> Fetch the complete documentation index at: https://docs.attention.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proactive

> Pull the Proactive actions Attention suggests for each rep — follow-ups to send, meetings to book, deal risks to address.

Proactive watches your calls, emails and CRM and suggests the next best action for each rep: a follow-up email to send, a meeting to book, a deal risk to address. Each action carries why it was suggested and, where it applies, a drafted message ready to send. The same actions appear on the **Actions** page in Attention.

These tools only return actions when Proactive is enabled for the user or the organization. Otherwise they return an empty list.

## Tools

### list\_proactive\_actions

> [!NOTE]
>
> Scope: `mcp:read`. Works with OAuth tokens, user-level API keys and org-level API keys.

List Proactive actions, newest first. Each action includes its title, type, status, severity, the deal or account it is about, why it was suggested (the rationale, a key quote and the supporting evidence), any drafted email (subject, body and recipients), proposed meeting times, and when it was generated and expires. Once an action has been drafted or sent, it also links to the result: the Gmail draft, document, deck or Slack message.

Who sees what follows the **Team** tab of the Actions page:

| Caller | Sees |
| - | - |
| Rep | Their own actions, in full. |
| Manager | Their own actions in full, plus the actions of the reps on their teams. |
| Admin | Their own actions in full, plus the actions of every rep in the organization. |
| Org-level API key | Every rep's actions, in full. |

When a signed-in manager or admin reads another rep's action, only its header comes back: title, type, status, owner and dates. The draft, recipients, proposed times, key quote and evidence stay with the rep who owns the action. Unlike the Team tab, which never lists expired actions, `status: ["expired"]` also returns other reps' expired actions, reduced to the same header.

**status** `array`

Lifecycle statuses to include: `pending`, `drafted`, `sent`, `completed`, `dismissed`, `expired`. Defaults to `pending`.

**owner\_uuid** `string`

Restrict to one rep's actions. Use a user ID from [`list_reps`](https://docs.attention.com/mcp/tools/users-roles#list_reps). An admin or an org-level API key can name anyone in the organization; a manager can name a rep on their teams. Ignored for a rep, who only sees their own.

**cursor** `string`

The cursor returned by a previous call, to fetch the next page.

**size** `integer`

Page size. Defaults to 50, maximum 200.

**Returns:** A Markdown list with one entry per action. When more actions are available, the result ends with the cursor to pass for the next page. When nothing matches, it returns an empty-state message; that also happens when Proactive is not enabled for the account.

**Example prompts:**

* *"What Proactive actions do I have pending this week?"*
* *"Show me the drafted follow-up for Acme and who it's going to."*
* *"Which reps on my team have the most pending actions?"*


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