ReachInbox
Sales OutreachReachInbox is a cold outreach platform with built-in deliverability tooling. Agents manage sending accounts and warmup, create campaigns and load leads, work replies in the unified Onebox, pull analytics, maintain the blocklist, and run inbox placement tests.
What This Integration Enables
ReachInbox is a cold outreach platform whose center of gravity is not the sequence. It is whether the mail arrives. The connector exposes the DNS records the platform expects for each sending account, a custom tracking domain verification check, warmup analytics per mailbox, and a full inbox placement testing surface with three test types including one that runs on a recurring schedule. Sixty-six operations cover the sending estate, the campaigns, saved lead lists that exist independently of any campaign, the unified Onebox, analytics, and the blocklist. Deliverability is treated as an ongoing measurement rather than a setup task, which is exactly the kind of state a machine should be watching and a person should be judging.
FlowRunner agents give that measurement somewhere to go. A flow can read placement results per provider, correlate them with each account's warmup health, check whether the expected authentication records are actually published, and pause the campaigns that are burning a domain before the reply rate tells you the same thing three weeks later. The connector itself listens for nothing, since ReachInbox exposes no event subscriptions here, so flows are driven by schedules and by events from the other systems in the stack. What arrives at a person is a decision with the evidence already assembled, which is the working definition of human-in-the-loop on this platform.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Placement drops before the reply rate does
An automated placement test repeats on its own schedule and Get Inbox Placement Results reports where the seed messages landed, broken out by provider. The agent sweeps those results, and when one provider's placement falls it does not stop at the number. It pulls Get Warmup Analytics for each sending account attached to the affected campaigns, and Get Account DNS Records to compare what the platform expects against what is actually published, including the DKIM selector that differs per provider. If the pattern points at a subset of mailboxes, Pause Campaign takes those campaigns off the wire while the rest keep running. The deliverability owner gets one message in Slack with the provider split, the accounts, and the specific record that does not match.
-
A saved list that becomes three campaigns without becoming three lists
Lead lists in ReachInbox hold leads independently of any campaign, and a lead copied onto a campaign becomes a separate record. That distinction is what makes segmentation safe. The agent maintains the master list with Update Lead List Lead as enrichment arrives from the CRM, then uses Copy Leads To Campaign to push segments onto campaigns that already have their sequences built. New replies detected in the Onebox update the source list, and interest status flows back to Pipedrive so the rep sees the same picture. The originals stay where they are, so a bad segment costs a campaign, not the list.
-
The Onebox as a triage queue rather than an inbox
List Onebox Threads reads replies across every connected account in one view. The agent classifies each thread. An out-of-office gets the lead's sequence resumed for a later date, and a referral to a colleague gets the new contact added and the original marked. Anything reading as a request to stop goes to Add To Blocklist first and is answered second. Reply keywords and outbound body keywords are separate lists on that operation, which matters, because an unsubscribe phrase belongs on the inbound side. Real replies get a draft assembled with the correct threading headers and posted for review. Interested threads are written to Attio with the conversation attached.
Human-in-Loop Highlight
The most dangerous thing in this connector is not a delete. It is a selector that looks empty. Update Accounts accepts the literal string ALL for its account ids, and it rewrites sender name, daily limits, sending delay, reply-to, signature, tracking domain, and the entire warmup configuration on everything it matches. Change Lead State, Delete Campaign Leads, and Mark Onebox Read go the other way: an empty id list combined with filters means every record those filters match, not none. A flow that meant to touch nothing and left the field out has just touched the workspace, and there is no undo for weeks of accumulated warmup reputation. So any bulk write in a FlowRunner flow resolves its selector first and reports the count in plain language. It posts: "Update Accounts is about to apply the new warmup schedule to 41 sending accounts, which is every mailbox in the workspace except the two tagged legal. The tag filter you gave matched 6. Apply to 41, apply to the 6, or stop?" A person confirms the number before the write goes out. The agent is fast at composing the change. It is not allowed to be fast at guessing the scope.
Agent Capabilities
66 actionsSending Accounts
10- List Accounts Lists the sending accounts connected to the workspace with their warmup health and connection state. The starting point for any estate-wide check.
- Get Accounts Overview Reads the workspace's sending accounts as a plain list, without the filtering and paging of the fuller listing.
- Get Account Info Reads one sending account's full settings: sender details, sending limits, warmup configuration, signature, and tracking domain.
- Get Account Mailboxes Lists the mailbox folders on a connected account, which is where a folder path for reading raw messages comes from.
- Create Account Connects a sending account over IMAP and SMTP. This path is for IMAP mailboxes only, because Google and Outlook credentials never reach the API.
- Get OAuth URL Returns the URL to send a user to so they can connect a Google or Outlook mailbox themselves. The only route for those providers.
- Update Account Connection Replaces one account's IMAP and SMTP settings. What to run after a password change or a server move.
- Update Accounts Changes settings across one or many sending accounts at once, including the whole warmup configuration. Its selector accepts a literal value meaning every account, so scope is a decision rather than a default. The operation this page's human gate exists for.
- Set Warmup State Turns warmup on or off across a selection of sending accounts, using the same selector rules as the bulk update.
- Delete Accounts Disconnects sending accounts from the workspace, either one at a time or by list.
Domain and Authentication
2- Get Account DNS Records Reads the SPF, DKIM, and DMARC records the platform expects for a set of sending accounts. The DKIM selector differs per provider and is part of the request rather than something the platform guesses.
- Check Custom Domain Status Reports whether a custom tracking domain is configured correctly. Worth running before pointing accounts at it, because an unverified tracking domain breaks every tracked link.
Campaigns
12- List Campaigns Lists the workspace's campaigns with their state and counters.
- Get Campaign Name Reads a campaign's name. The cheapest way to confirm an id points at what a flow thinks it does.
- Get Campaign Status Reads whether a campaign is running, paused, completed, or still a draft. What to poll after starting one.
- Get Campaign Accounts Lists the sending accounts a campaign sends from. A campaign with none attached cannot start.
- Create Campaign Creates an empty campaign and returns its id. It has no sequence, leads, or sending accounts yet, and the sequence itself is built in the platform.
- Duplicate Campaign Copies a campaign including its sequence under a new name. How a proven sequence becomes the starting point for the next one.
- Rename Campaign Changes a campaign's name.
- Start Campaign Starts a campaign sending to its leads on its sequence's schedule. There is no confirmation step, and pausing is what stops it again.
- Pause Campaign Stops a running campaign. Mail already sent stays sent, and the sequence resumes where it left off if the campaign starts again.
- Set Campaign Accounts Replaces the set of sending accounts a campaign uses. An account left out is detached, so a flow that means to add one reads the current set first.
- Add Campaign Accounts Attaches sending accounts to a campaign without disturbing the ones already there.
- Remove Campaign Account Detaches one sending account from a campaign, by a single address rather than a list.
Campaign Leads
6- List Campaign Leads Reads the leads on a campaign with their state.
- Get Campaign Lead Reads one lead on a campaign, with its attributes and where it has reached in the sequence.
- Add Campaign Leads Adds leads to a campaign. Any custom attribute must also be declared as a column, and the duplicate handling decides what happens to addresses already on the campaign.
- Update Campaign Lead Changes one lead's attributes or its interest status on a campaign.
- Change Lead State Pauses, resumes, stops, or completes leads in bulk. An empty id list combined with filters means every lead those filters match, so the selector is always resolved before the call.
- Delete Campaign Leads Removes leads from a campaign, with the same selector rule as the bulk state change.
Lead Lists
9- List Lead Lists Lists the workspace's saved lead lists, which hold leads independently of any campaign.
- Get Lead List Reads one lead list's details.
- Get Lead List Leads Reads a page of the leads inside a list.
- Create Lead List Creates an empty lead list and returns its id.
- Rename Lead List Changes a lead list's name.
- Update Lead List Lead Changes one lead's attributes inside the list. This edits the master record, not any campaign copy, since a copied lead is a separate record.
- Copy Leads To Campaign Copies leads from a saved list onto a campaign. The originals stay in the list, which is what makes segmentation reversible.
- Delete Lead List Leads Removes leads from a list. Its id field accepts a literal value meaning every lead, with exclusions carved back out.
- Delete Lead List Deletes a lead list and the leads inside it. Leads already copied onto a campaign are separate records and stay there.
Onebox
5- List Onebox Threads Reads the unified inbox across every connected account, filtered by campaign, account, folder, and free text.
- Get Onebox Thread Reads one conversation in full, identified by its message id rather than a numeric key, scoped to the account that holds it.
- Get Onebox Messages Reads a page of raw messages from one folder of a connected mailbox.
- Send Onebox Reply Sends an email from a connected account, normally as a reply inside an existing conversation. Correct threading depends on carrying the reply headers from the message being answered, or the recipient's client shows a new conversation.
- Mark Onebox Read Marks conversations as read. An empty campaign list means every conversation in the workspace, so the campaigns are named deliberately.
Analytics
3- Get Campaign Analytics Reads a campaign's performance over a date range. Subsequences are counted only when they are named explicitly.
- Get Analytics Summary Reads workspace-wide totals over a date range, with exclusions rather than inclusions as the way to leave a campaign out.
- Get Warmup Analytics Reads how a sending account's warmup is performing. The number to check before pointing a campaign at that account.
Blocklist
3- Add To Blocklist Blocks addresses, whole domains, or messages matching keywords. Outbound body keywords and inbound reply keywords are separate lists, and an unsubscribe phrase belongs on the inbound side.
- List Blocklist Keywords Reads the blocked keywords with the ids their removal requires.
- Delete Blocklist Keywords Removes blocked keywords by id.
Inbox Placement
10- List Inbox Placement Tests Lists deliverability tests and where each has got to.
- Get Inbox Placement Test Reads one test's configuration.
- Get Inbox Placement Results Reads where the seed messages landed, per provider. The number a warmup change or a domain change is judged on.
- Create Inbox Placement Test Creates a test. It arrives empty, with seeds, content, and schedule set separately before it can run.
- Update Inbox Placement Test Configures a test. The test type decides which parameters mean anything, and a field belonging to a different type is ignored rather than refused.
- Rename Inbox Placement Test Changes a test's name and description.
- Duplicate Inbox Placement Test Copies a test's configuration under a new name.
- Start Inbox Placement Test Runs a test, which sends the seed message from the configured sending accounts to the seed mailboxes.
- Set Automated Test State Pauses or resumes an automated test's recurring schedule. Applies to automated tests only, since a manual one has no schedule.
- Delete Inbox Placement Test Deletes a test and its results.
Tags
6- List Tags Lists the workspace's tags with their ids and descriptions.
- Create Tags Creates one or more tags. A tag has to exist before it can be attached.
- Add Tags To Campaign Attaches tags to a campaign by name.
- Remove Tag From Campaign Detaches one tag from a campaign by its numeric id, which is the opposite of how attaching works.
- Add Tags To Accounts Attaches tags to sending accounts. Those tags are what the tag filters on account listings and warmup changes match against.
- Remove Tag From Accounts Detaches one tag from sending accounts by numeric id.
Frequently Asked Questions
What can FlowRunner do with ReachInbox?
FlowRunner agents can run List Accounts, Get Accounts Overview, and Get Account Info in ReachInbox, plus 63 more actions.
Does connecting ReachInbox to FlowRunner require OAuth?
No. ReachInbox connects to FlowRunner with an API key, no OAuth flow required.
Can ReachInbox trigger a FlowRunner workflow automatically?
ReachInbox doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with ReachInbox
Free plan, no card required. Connect in minutes.