> 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/integrations/output-integrations/messaging-tools/outreach.md).
# Outreach
Reo.Dev’s **Outreach.io integration** allows GTM teams to seamlessly connect with prospects, enabling efficient engagement with **buyers and developers** through automated email sequences and campaigns.
With this integration, you can:
* **Directly add prospects** from Reo.Dev to Outreach.io sequences.
* **Run targeted email campaigns** for developer segments in Reo.Dev
#### **Prerequisites**
{% hint style="warning" %}
**You must be an Admin in both Reo.Dev and** Outreach.io to complete this integration.
{% endhint %}
***
**Step 1:** Log in to your **Reo.Dev Admin account**.
**Step 2:** Click on **Integrations -> Messagin tools -> Connect under Outreach**
**Step 3**: Sign in to your Outreach.io **account** to which you wish to connect.
{% hint style="info" %}
**Note:** You must have an **Admin role in Outreach.io** to complete this integration successfully.
{% endhint %}
**Step 4:**
* After signing in to your Outreach.io account, you will see a confirmation screen indicating that your Outreach app is successfully connected to Reo.Dev.
* Click **"Click to config"** to proceed with configuring your sequence settings.
#### **Configure Sequence Settings**
* Once connected, Reo.Dev will fetch all your Outreach.io **sequences**.
* Choose which sequences to activate and surface in Reo.Dev.
* Click **Save** to confirm the setup.
#### **6. Configure Sequence Ownership**
You can choose whether a sequence is **Private** or **Shared**.\
\
**Private Sequences**
* Visible only to the owner by default.
* Other users cannot find or use the sequence.
* An admin can optionally allow certain user profiles to discover and use private sequences.
**Shared Sequences**
* Accessible to other users in the workspace.
* Others can find and use the sequence (based on your organization’s visibility rules).
* Admins can further restrict visibility so users only see sequences that belong to the same Collection as their team.
**In Short**
* Owner = Who is responsible for the sequence.
* Private = Only you (and optionally admins/allowed profiles) can see and use it.
* Shared = Your team can find and use it, with visibility optionally limited by Collections.\
#### **7. Editing Your Integration Settings**
* You can click on the gear icon to adjust your sequence settings.
{% hint style="success" %}
If unsure which sequences to enable for each profile, you can set them up later by revisiting this settings page.
{% endhint %}
***
### **Step 2: Using** Outreach.io **Integration in Reo.Dev**
#### **Use Case 1: Adding Buyers or Developers to an** Outreach.io **Sequence**
**Best for:** SDRs engaging decision-makers in ICP accounts.
#### **1. Navigate to the Accounts Panel**
* Click on **Accounts** and select an account of interest.
* Go to the **More Prospects** tab.
#### **2. Add Buyers to an** Outreach.io **Sequence**
* Select the buyers from the Revealed tab and click **Add to Outreach Sequence**.
* In the **popup modal**:
* **Choose the** Outreach.io **sequence** from the dropdown that best matches this cohort.
* **Select the email inbox** to send emails from.
* Click **Send to Sequence** to initiate outreach.
{% hint style="info" %}
**Only Verified Business Emails Are Enrolled**
Reo.Dev only enrolls prospects who have verified business emails. If a selected buyer/developer does not have a valid business email, they will **not be added** to the Outreach.io sequence.
{% endhint %}
***
#### **Use Case 2: Running an Email Broadcast Campaign for Developers**
**Best for:** Automating outreach to engaged developers in your ecosystem.
#### **1. Navigate to Campaigns**
* Click **Tools → Campaigns** in the sidebar.
* Click **Create** in the top-right.
#### **2. Configure Your Outreach Campaign**
* In the **popup modal**:
* **Campaign Name**: Enter a relevant name (e.g., “Retargeting High-Intent Developers”).
* **Segment Name**: Select a **developer-based segment** created in Reo.Dev (not an account-based one).
* **Channel**: Choose Outreach.io.
* **Sequence**: Select the Outreach.io **sequence** for this segment.
* **Send Email From**: Choose the sending inbox.
* **Check "Do not add prospects already in an active sequence"** (Best practice to prevent spam).
* Click **Create** to launch the campaign.
***
{% hint style="info" %}
#### **Only Developers with Verified Business Emails Are Enrolled**
When running developer outreach campaigns, Reo.Dev **only adds developers who have verified business emails** to the Outreach.io sequence. Developers without a valid business email **will not be enrolled**.
{% endhint %}
***
### **How Reo.Dev Automates Developer Outreach**
Once the campaign is set up, **this process becomes dynamic** in Reo.Dev:
* Whenever a **new developer meets the criteria** of the selected segment, they are **automatically added** to the segment.
* This means they will **also be automatically added** to the connected Outreach.io sequence **without manual intervention**.
* The syncing happens **every 24 hours**, ensuring new developers are enrolled into the sequence seamlessly.
***
🔗 **To learn more on bulk email campaigns, refer to this guide below**:\
[Running Bulk Email Campaigns](/campaigns/run-bulk-email-campaigns.md)
***
### **Important Note on** Outreach.io **Sequence Throttling & Sending Limits**
When adding prospects to Outreach.io sequences through Reo.Dev, the **sending behavior depends on Outreach.io’s throttle limits and lead statuses** (e.g., **Pending, Active, Finished**).
{% hint style="warning" %}
**Make sure to configure your** Outreach.io **sequence throttling settings properly** to avoid exceeding daily send limits.
{% endhint %}
🔗 **Refer to Outreach.io’s official guide on sequence throttling and sending limits**:\
[How to Configure Outreach Sequence Throttles](https://support.outreach.io/hc/en-us/articles/205107348-How-To-Configure-Outreach-Sequence-Throttles)
***
### **Final Notes & Best Practices**
* **Segment buyers & developers separately** for higher engagement rates.
* **Regularly monitor** Outreach.io **sequences** to track performance.
* **Ensure your** Outreach.io **throttling settings are optimized** for efficient email delivery.
***
#### **Additional Testing Guide for Reo.Dev**
To ensure your email integration is working end-to-end, including how Reo.Dev syncs data with Outreach.io and how emails are triggered, refer to our **detailed testing guide:**
[Testing Your Email Integration with Reo.Dev](/campaigns/testing-your-email-integration-with-reo.dev.md)
---
# 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:
```
GET https://docs.reo.dev/integrations/output-integrations/messaging-tools/outreach.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.