Agents handle repetitive CRM work automatically — updating deal stages after calls, routing new leads, posting weekly pipeline summaries — without manual input. Configure an agent once and it runs in the background every time its trigger fires.
Agents are available to all Clarify users during the beta period. Limits on the number of agents per workspace may be introduced before general availability. To get started, click the Agents link in the left sidebar.
What is an agent?
An agent is a background worker in Clarify built around three things:
Trigger — what causes the agent to run (a record change, a time schedule, a webhook, or another CRM event)
Instructions — what the agent does each time it runs
Tools and access — which data and integrations the agent can use
Unlike Rep, which responds to your messages, agents run automatically without any input from you.
How agents work
Agents run automatically in the background. Once configured, they fire whenever the trigger condition is met.
Go to Agents → select Add Agent — describe what you want in plain English (for example, "after every sales call, update the deal stage and log next steps"), or choose a template from the gallery
Rep builds the agent — it pre-fills the trigger, writes the instructions, and selects the tools based on what you described
Review and enable it — the agent is inactive until you enable it
It runs automatically — every time the trigger fires, the agent executes its instructions using the tools you've allowed
Stay informed — receive in-app notifications and Slack notifications when the agent acts or needs your approval
Available triggers
Add filters to any trigger to narrow when the agent runs — for example, trigger only when a deal moves to a specific stage, or only for records assigned to you.
Trigger | Description |
Record created | Fires when a new person, company, deal, meeting, or custom object is created |
Record updated | Fires when a record's fields change |
Record deleted | Fires when a record is deleted |
Added to list | Fires when a record is added to a specific list |
Removed from list | Fires when a record is removed from a list |
Relationship set | Fires when a relationship is created between two records |
Relationship changed | Fires when an existing relationship between records changes |
Webhook | Fires when an external service sends data to a unique URL generated for your agent |
Schedule | Fires on a recurring schedule (e.g. every weekday at 9am) |
Create an agent
Select Add Agent from the Agents screen.
Describe what you want — type what the agent should do in plain English, or choose a template from the gallery to start from a pre-built agent.
Answer up to three clarifying questions — if your description leaves details open, Rep asks follow-up questions with suggested options: for example, what counts as a high-value deal, how you want to be alerted, and whether the agent should act automatically or ask for your approval first. Select an option or type a custom answer.
Wait while the agent builds — Rep checks for existing agents, fetches your CRM schema, and generates the trigger, instructions, and tools configuration. The finished agent appears on the right side of the screen with an auto-generated name and description.
Review and enable — the agent is inactive by default. Adjust the trigger, instructions, or tools if anything doesn't look right, then toggle Enable to activate it.
Human-in-the-loop
Set any tool or action to require your approval before it runs. The agent will pause, notify you, and wait. Approve or deny in-app — no need to re-run the whole agent.
When an agent needs your input, you'll be notified two ways:
In-app notification — a notification inside Clarify letting you know the agent is waiting
Slack — notifications can go to a Slack DM or post directly to a channel. Configure this in Settings > Rep > Tools > Slack.
Tools and access
Agents are scoped to their creator's permissions. An agent can only see records, emails, and integrations that its creator has access to.
Run agent
To test a new agent or kick off a run outside the normal trigger schedule, use the Run agent button inside the agent. Each manual run counts against your credit usage and rate limit.
Activity log
Every agent has an activity log showing a full history of its runs — when it ran, what triggered it, what actions it took, and how many credits it used. Expand any run entry to see the agent's step-by-step reasoning.
Limitations
⚠️ There is no undo for agent actions. If an agent updates a record incorrectly, open Rep in the agent's chat and ask it to revert the specific change. This is the most significant limitation in the current beta. Use approval mode until you're confident in an agent's behavior — it lets you review each action before it executes.
Additional current limitations:
No cancel mid-run. Once a run starts, it runs to completion. Enable approval mode if you're concerned about an agent acting too broadly.
Historical data is limited. Agents act on new data going forward by default. Processing historical records is possible but capped per run — each run supports up to 30 processing steps, and each step can retrieve up to 25 records. A user-configurable turn limit is coming.
Per-agent usage tracking is coming. Credit breakdowns per agent are in progress and will be available before general availability.
No exportable audit log yet. The in-app activity log is the current record of agent actions.
Rep and agents working together
Rep is the conversational layer on top of everything agents do.
Rep builds agents. Describe what you want and Rep creates it.
Rep debugs agents. If something doesn't work as expected, describe the problem to Rep and it will suggest fixes.
Rep answers questions about agent activity. Ask "what did the pipeline review agent do this week?" and Rep will summarize the run history.
Rep can delete agents. Ask Rep to delete an agent by name from chat.
What you can build
Here are examples of agents early access customers are already running.
Agent | What it does | Who it's for |
Post-call CRM updater | After every sales call, reads the transcript and updates deal stage, next steps, and custom fields automatically | Sales reps who spend time on manual CRM updates after calls |
Inbound lead router | When a new lead is created, enriches the record with web research and assigns it to the right owner based on company size or geo | GTM ops and RevOps teams managing high inbound volume |
Weekly pipeline briefing | Every Monday morning, posts a structured pipeline summary to your Slack channel | Sales managers and founders who want a pulse on the week ahead |
Meeting follow-up drafter | After a customer call, drafts a follow-up email and saves it to your email drafts for review before sending | Account executives and CSMs who send follow-up emails after every call |
Product feedback logger | Scans meeting recordings and inbound emails for product feedback and logs them as structured records in Clarify | Product and ops teams building a feedback loop from customer conversations |
Daily briefing | Every morning, compiles your meetings for the day, open tasks, recent pipeline changes, and emails that need attention | Founders and GTM leads who want a single daily digest |
Available tools
Connect tools in Settings > Rep > Tools, then set allow, require approval, or deny per tool per agent.
Clarify CRM
The core tool for reading and writing your CRM data.
What an agent can do:
Read company, person, deal, meeting, and task records
Update fields, deal stages, labels, and custom fields
Create new records (companies, people, deals, tasks)
Deduplicate and merge records
Route new leads to the right owner based on geography, size, or segment
Log structured notes and follow-up tasks from meeting transcripts
What it cannot do:
Access records the agent owner doesn't have permission to view
Permanently delete records
Modify workspace settings or user permissions
Email (Gmail or Outlook)
Connects to your email account for reading and drafting email.
What an agent can do:
Read inbound emails and identify opportunities or required responses
Draft email replies and save them to your email drafts for review
Send emails automatically when configured to do so
Create deal records from email buying signals
Draft outreach or follow-up emails based on CRM data and web research
What it cannot do:
Draft or send emails from a colleague's inbox — only the agent owner's account
Access emails in other connected accounts
Delete emails
Slack
Connects to your Slack workspace for posting messages and reading channel activity.
What an agent can do:
Post messages to any Slack channel the owner has access to
Send a direct message to yourself or others
Post structured summaries, briefings, and pipeline reviews
Read Slack messages and react to events in Slack
What it cannot do:
Post to channels the agent owner isn't a member of
Send messages as another user
Create or archive channels
Requires your Slack workspace to be connected first (Settings > Connected accounts > Slack).
Granola
Connects to your Granola meeting notes for reading transcripts and extracted content.
What an agent can do:
Read meeting notes and transcripts created in Granola
Extract action items, decisions, and key topics from notes
Use meeting content as context for updating CRM records or drafting follow-ups
What it cannot do:
Create or edit notes inside Granola
Access notes from meetings the owner wasn't part of
Notion
Connects to your Notion workspace for reading and updating pages and databases.
What an agent can do:
Read pages and database entries
Create new pages and database records
Update existing page content
Write documentation, briefings, or summaries directly into Notion
Sync CRM data into a Notion database
What it cannot do:
Access pages the agent owner doesn't have permission to view
Delete pages or databases
Modify workspace settings or sharing permissions
Linear
Connects to your Linear workspace for reading and creating issues.
What an agent can do:
Read existing issues, projects, and team data
Create new issues from meeting notes, emails, or CRM activity
Add comments to issues
Update issue status and assignees
What it cannot do:
Delete issues
Modify team or workspace settings
Access issues in teams the agent owner doesn't belong to
Web search
Built-in — no setup required.
What an agent can do:
Search for company news, funding announcements, and job changes
Research a prospect or account before outreach
Pull recent information to add to a briefing or summary
What it cannot do:
Access pages behind a login or paywall
Submit forms or interact with websites
Store or remember search results across runs
Custom MCP servers
For teams that want to connect agents to tools not listed above.
What an agent can do:
Connect to any remote MCP server your workspace configures (OAuth or API token over HTTP)
Use any tools exposed by that server within agent instructions
What it cannot do:
Connect to local npm/stdio MCP servers (not yet supported)
Bypass the tool permission settings configured in Settings > Rep > Tools
Contact Clarify support to set up a custom MCP server connection.
Sharing and visibility
All agents are visible to everyone in your workspace. Anyone can see the agent's name, trigger, instructions, and tools.
The private/public toggle controls who can see the agent's activity — its run history, reasoning steps, and Clarify chat. Set it to public to let teammates follow along; keep it private if the agent's activity contains sensitive information.
Only the creator can edit an agent's instructions, triggers, tools, or toggle it on or off.
Workspace admins have the same access as any other user. They can view all agents and their activity but cannot edit agents they don't own.
Anyone in the workspace can duplicate an agent. The person who duplicates it becomes the new owner — it runs using their permissions and tool connections.
To delete an agent, ask Rep: "delete [agent name]."
Credits and billing
⚠️ During early access beta, agents are not billed. Build and run agents freely while we work on the billing experience. From June 1st, agent runs will consume credits from your workspace credit pool. All early access customers will receive an email notification before this change takes effect.
How agent credit costs work
Agent costs are based on actual AI usage per run. Shorter, simpler interactions cost less than longer, multi-step ones.
Factors that affect cost:
Amount of data read — querying a few records costs less than scanning your entire pipeline
Number of actions taken — a single comment costs less than creating records + sending emails + posting to Slack
Conversation complexity — multi-step reasoning with back-and-forth tool calls uses more than a single lookup
Example agent costs
Agent type | Typical cost per run | Runs per 1,000 credits |
Post-call CRM updater | ~5–15 credits | ~65–200 |
Data enrichment + record creation (e.g. inbound lead router) | ~10–25 credits | ~40–100 |
Multi-step analysis + drafting (e.g. pipeline briefing) | ~15–40 credits | ~25–65 |
Complex multi-tool workflow (e.g. research + create + email + Slack) | ~30–60 credits | ~15–35 |
Costs are estimates. Actual usage varies based on data volume and conversation length.
Tracking usage
Monitor agent credit usage in Settings > Billing. It shows total credit usage across Rep and all agents.
Per-agent credit cost tracking is coming soon and will be available before general availability.
Rate limits
Each agent is limited to 100 runs per hour. This prevents runaway automations from consuming large amounts of credits unexpectedly.
FAQ
Can I stop an agent once it's running?
Not yet — once an agent run starts, it runs to completion. Canceling a mid-run agent is on our roadmap. In the meantime, enable approval mode so the agent pauses and asks before taking any action.
What happens if an agent updates a record incorrectly?
There's no undo button in the notification or activity log. To undo a change, open Rep in the agent's chat and ask it to undo the specific change. This is the most important limitation in the current beta — see the Limitations section above for more detail.
Who can see my agents?
All agents are visible to everyone in your workspace. The private/public toggle controls who can see the agent's activity (run history and chat logs) — not the agent itself. Only the creator can edit or toggle an agent.
Can my teammates use my agents?
Anyone in your workspace can view and duplicate your agent. When someone duplicates it, they become the owner and it runs using their permissions and tool connections. Agents always run as their owner — access to records and integrations is scoped to whoever owns the agent.
Will I get notified when an agent runs?
Only when an agent acts or needs your approval. You'll receive an in-app notification and a Slack notification (DM or channel, based on your settings) if your Slack workspace is connected. There are no email notifications. View the full run history and records touched in the agent's activity log.
Can agents send emails on my behalf?
Agents can draft emails and save them to your email drafts for review — or send automatically if configured to do so. All sends go via your email account. An agent cannot draft or send from a colleague's inbox.
What integrations do agents support?
Agents connect to Slack, Notion, Linear, Gmail and Outlook, Granola, and any custom MCP server your workspace configures. Web search is also available as a built-in tool. Connect tools in Settings > Rep > Tools, where you can set allow, require approval, or deny per tool per agent. More connectors are on the roadmap.
Can agents process my historical CRM data?
Agents act on new data going forward by default. Processing historical records is possible but limited by a per-run cap. Contact support if you need to process a large historical backfill.
How do credits work after June 1st?
Agent runs and Rep usage both draw from your workspace credit pool. Costs are based on actual AI usage — shorter, simpler runs cost less. See the Example agent costs table above for typical ranges. A per-agent billing dashboard is in progress and will be available before general availability.
Can an agent trigger another agent?
Yes — if an agent creates or updates a record, that change can trigger another agent. Clarify automatically prevents recursive loops: after five chained triggers, the chain stops and no further agents are triggered.
What happens if my agent hits the rate limit?
Each agent is limited to 100 runs per hour. New trigger events are dropped until the hourly window resets. The agent resumes on the next trigger after the reset.
What plan do I need to access Agents?
Agents are available to all Clarify users during the beta period. Limits on the number of agents per workspace may be introduced before general availability.
Where do I find Agents in Clarify?
Agents are accessible via the Agents link in the left sidebar.