> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/playbooks/agents/how-to-use-reo-agents-in-your-daily-workflows.md).
# How to Use Reo Agents in Your Daily Workflows
Reo Agents help you find and monitor accounts and developers based on the GTM signals that matter to you - so you always know who to prioritize, when to act, and what workflow to trigger next.
In this playbook, we’ll walk through the different ways you can use Agents and plug them into your daily workflows or external tools. The goal is simple: set it up once, and let Reo continuously surface the right accounts for action.
Before we get into the workflows, here’s a quick overview of the different types of Agents you can build in Reo.Dev and what you can do with their findings.
### Types of Agents in Reo.Dev
There are two types of Agents in Reo.Dev: **Chat Agents** and **Pre-built Agents**.
#### 1. Chat Agents
Chat Agents let you build custom agents using simple prompts. You can use them in two ways:
* **Discover net-new accounts**
Use this when you want to find new accounts based on specific GTM signals, including accounts that may not already be tracked in Reo.
For example, you can ask Reo to find companies that are hiring DevOps leaders, scaling AI/ML teams, migrating from a competitor, or showing signs of engineering investment.
{% hint style="info" %}
💡 Note: Once the Agent finds matching accounts, you can save them directly as a list and start taking action on them.
{% endhint %}
* **Enrich existing account segments or lists**
Use this when you already have a target account list, open pipeline, CRM-owned account segment, or strategic account list — and you want to identify which accounts match a specific high-value signal.
For example, you can run an Agent across your target accounts to find which ones are hiring platform engineers, expanding their security team, or showing signs of competitor migration.
{% hint style="info" %}
💡 Note: Once the Agent has enriched your accounts, create a segment using the **Account Agent Tags** filter. This enables you to run follow-up workflows on them.
{% endhint %}
#### 2. Pre-built Agents
Pre-built Agents are ready-to-use Agents that help you monitor your accounts or developers for common GTM signals.
Use this when you want to quickly run a known signal across a segment or list without building a custom Agent from scratch.
{% hint style="info" %}
💡 Note: Once the Agent finds matching accounts, we recommend creating a segment using the **Account Agent Tags** filter. From there, you can plug those accounts into alerts, CRM workflows, webhooks, or Claude-powered workflows.
{% endhint %}
[Here’s the complete guide on how to create agents](https://docs.reo.dev/agents)
### Ways to Action on Agent Findings
Once you’ve built or deployed an Agent, there are multiple ways to use the findings in your day-to-day workflows.
#### 1. Set up alerts for new Agent findings
**Use this when:** you want to stay updated whenever an Agent finds a new matching account or developer.
You can set up automations to receive Slack or email alerts whenever there are new Agent findings.
To set this up:
1. Go to **Automations**
2. Choose the segment or list you want to monitor
3. Select the trigger: **New Finds by Agents**
4. Choose the relevant Agent tag
5. Set up the alert channel — Slack or email
You can use these alerts to notify the right sales rep, route accounts to the right owner, or take immediate action based on the signal.
[Here’s the complete guide on setting up automations](https://docs.reo.dev/automations)
#### 2. Send Agent matches to other tools using webhooks
**Use this when:** you want to send Agent findings into external tools or trigger workflows outside Reo.
You can use Agent tags to trigger a webhook and send matched accounts directly into your preferred system.
For example, you can use webhooks to send Agent-matched accounts into tools for routing, enrichment, scoring, sequencing, or campaign activation.
How it works:
1. Create a segment using the relevant **Account Agent Tag**
2. Set up an automation on that segment
3. Choose webhook as the action
4. Send matched accounts into your external workflow
This is useful when you want Reo’s Agent findings to power workflows across your broader GTM stack.
[Here’s the complete guide on how to create a webhook](https://docs.reo.dev/integrations/output-integrations/data-export/webhooks#creating-a-webhook)
#### 3. Sync Agent data to your CRM
**Use this when:** your sales team primarily works out of your CRM.
You can sync Agent-enriched segments to your CRM and use Reo’s Agent tags to power CRM-based workflows.
For example, you can use Agent tags to:
* Enroll accounts into specific CRM workflows
* Update lead or account scoring models
* Trigger sales sequences
* Assign accounts to reps
* Create follow-up tasks
* Prioritize open pipeline accounts
To set this up:
1. Create a segment using the relevant **Account Agent Tag**
2. Sync the segment to your CRM
3. Use the Agent tag field in your CRM to trigger workflows, scoring, routing, or sequences
This helps your reps act on Agent findings without needing to constantly check Reo.
#### 4. Use the Reo MCP Claude Connector to act on Agent findings
**Use this when:** you want to use Claude to research, prioritize, or act on Agent-matched accounts at scale.
Once you create a segment or list from Agent findings, you can use the Reo MCP Claude Connector to ask questions and take action on those accounts directly from Claude.
For example, you can ask Claude to:
* Find the best buyers in Agent-matched accounts
* Identify the most active accounts in a segment
* Research each account and summarize why it is relevant
* Create account briefs for sales reps
* Suggest outreach angles based on the Agent signal
* Prioritize accounts based on activity, fit, and intent
* Prep reps for upcoming calls
To get started:
1. Create a segment or list using Agent findings
2. Open Claude with the Reo MCP Connector enabled
3. Ask Claude to analyze, prioritize, or enrich those accounts using Reo data
This is especially useful when you want to turn Agent findings into account research, buyer discovery, sales prep, or outreach workflows.
***
With this setup, Reo Agents continuously monitor the signals that matter to your business and push the right accounts into the right workflows — so your team can act faster, with better context.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.reo.dev/playbooks/agents/how-to-use-reo-agents-in-your-daily-workflows.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.