SalesBlink
Sales OutreachRun AI cold email outreach with SalesBlink, covering prospect lists and leads, multi-step sequences, the unified inbox, and send activity. Agents keep sequences supplied and replies routed.
What This Integration Enables
The setting that distinguishes SalesBlink is evergreen. A sequence can be configured to keep pulling new leads as its lists grow, which turns outbound from a series of discrete sends into a standing arrangement: define it once, keep feeding the list, and the machine keeps going. That is genuinely useful and it is also the thing worth being careful about, because the human decision moves from "send this batch" to "authorize this pattern indefinitely." SalesBlink pairs it with two other settings that make the pattern survivable: verification gating so only valid addresses are contacted, and a reply-stop scope that can halt everyone at a domain the moment one person there answers.
FlowRunner agents drive the whole workspace through connectors. They create and archive prospect lists with verification and duplicate-removal rules, and move a lead between a staging list and the list a live sequence draws from. They clone a proven sequence and repoint it, then pause and resume it without losing anyone's position. They work a unified inbox filtered by sequence, sender, outcome and read state, and pull sent, open, click and reply activity as separate logs. Agencies get workspace and user management in the same connector. What FlowRunner supplies is the human-in-the-loop discipline around the one decision that is not a batch decision.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Staging list to live list as a promotion
Rather than pointing a live sequence at a raw import, the agent uses two lists. New leads land in a staging list created with verification enabled, so invalid and risky results are archived out automatically and duplicate removal is scoped across the whole workspace rather than one list. The agent reads the survivors with Get List Leads, enriches missing fields, and calls Move Lead to promote each verified contact into the list the live sequence draws from. Promotion becomes an explicit act with a checkpoint in front of it, instead of an import that starts sending before anyone has looked at it.
Running the same playbook against a new segment
A sequence performs well for one vertical. Instead of rebuilding it, the agent calls Clone Sequence, which produces a copy that starts paused, then repoints the clone at the new segment's list and the senders that should carry it with Update Sequence. Get Sequence confirms the step order, schedule, delay window and reply-stop behaviour came across intact. Only when a person has approved the new targeting does the flow unpause it. The playbook is reused and the aim is re-verified, which are two different things.
Inbox outcomes written once, read everywhere
A flow polls Get Inbox Threads filtered to replies only and unread, pulls the exchange with Get Thread Messages, and classifies each conversation. It writes the classification back with Update Mail State so SalesBlink's own reporting reflects reality, records the outcome on the matching HubSpot record, and notifies the owning rep in Slack with the prospect's actual words attached. Approved replies go out through Send Reply from the mailbox that owns the thread. Nobody triages the same inbox twice.
Human-in-Loop Highlight
Create Sequence with the evergreen setting on is not an approval to send a batch. It is an approval to keep sending, on this copy, from these mailboxes, to whoever ends up in a list that other systems will keep filling for months. The same call also decides whether a reply from one person stops just that contact or everyone at their domain, and whether sending is gated on verification results at all. Every one of those choices has consequences that arrive long after the flow that made them has finished running. So the agent prepares the whole configuration and stops before committing it: "New sequence 'DACH Logistics' would attach 4 senders, pull from list 'DACH verified' which currently holds 612 leads and is fed weekly by the enrichment flow, gate on verification, and stop the whole domain on a reply. Evergreen is on, so it will keep enrolling as the list grows. Approve as evergreen, restrict to the 612 in hand, or change the reply-stop scope first?" A person answers, because an open-ended authorization deserves a signature and a batch does not. Once it exists, the standing correction is Update Sequence with Paused on, which halts sending while leaving every prospect's position intact.
Agent Capabilities
35 actionsLists
10- Get Lists Returns the prospect lists on the workspace with contact count, starred and archived flags, owner and last modified time. Filter by name, star or archive state, or by the team member who owns the list.
- Create List Creates a prospect list, optionally filed into a folder and starred. Verification can be switched on so imported addresses are checked automatically, with invalid and risky results archived out. Duplicate removal can be scoped to this list, to all your lists, or across team members' lists.
- Get List Retrieves one list by id with its name, contact count, starred and archived state, owner and last modified time.
- Update List Applies a partial update: rename, star, or change verification and duplicate-removal behaviour. Only supplied fields are written.
- Archive List Archives or unarchives a list. Archived lists are hidden from the default view and stop feeding new prospects into sequences, while their contacts are preserved.
- Get List Leads Returns the leads held in a list with their contact fields, paged and optionally narrowed to a single team member's records. This is how a flow reads what survived an import with verification enabled.
- Add Leads To List Imports contacts into a list. Each contact is a flat object of field names to values covering First_Name, Last_Name, Email, Company, Title, Phone and any custom columns the templates reference. Duplicate removal can be applied during the import.
- Remove Lead From List Removes a contact from a list by email address, so the lead stops being fed into sequences drawing from it.
- Update Lead Applies a partial update to a lead record, so a single corrected title or a newly found phone number can be pushed without restating the rest.
- Move Lead Moves a lead from one prospect list to another. This is how a verified contact gets promoted out of a staging list into the list a live sequence draws from, which makes enrolment an explicit act rather than a side effect of import.
Sequences
7- Get Sequences Returns the sequences on the workspace with paused, starred and archived flags, owner, and headline counters for sends, opens, clicks and replies. Filter by status, name, star or archive state, or owner.
- Create Sequence Creates a sequence bound to sending mailboxes and prospect lists. This one call decides several things at once: whether it launches now or at a scheduled time, the randomised inter-send delay window, and whether sending is gated on verification results. It also sets whether a reply stops just that contact or everyone at their domain, and whether the sequence is evergreen and keeps pulling new leads as its lists grow.
- Get Sequence Retrieves one sequence with its full configuration: attached senders and lists, ordered steps, schedule and sending hours, delay window, reply-stop behaviour, verification gating and tracking settings.
- Update Sequence Applies a partial update, including pausing and resuming. Setting Paused on halts sending while leaving each prospect's position intact, and turning it off resumes from the same step. This is the standing correction for a sequence already in flight.
- Get Sequence Stats Returns sends, opens, clicks and replies plus a lead funnel breakdown of how many prospects have not started, are in progress, have completed or are blocked. Restrict to a date range or to a single mailbox.
- Clone Sequence Creates a copy of an existing sequence with its steps and settings intact. The clone starts paused so its lists and senders can be repointed before launch, which is the usual way to run the same playbook against a new segment.
- Archive Sequence Archives or unarchives a sequence. Archiving removes it from the default view but does not stop sending on its own, so combine it with pausing when the intent is to halt.
Inbox
4- Get Inbox Threads Returns unified inbox threads across the workspace: all activity, replies only, or sent only. Narrow by sequence, mailbox, free text, recorded outcome, unread state, star and archive flags, or to the last N days.
- Get Thread Messages Returns every message in one thread in order, so a flow can read the full exchange before drafting a reply or classifying the conversation.
- Send Reply Sends a reply into an existing thread from the mailbox that owns it, optionally copying additional recipients, keeping the exchange in the conversation the prospect already sees.
- Update Mail State Marks a thread read or unread and records an outcome against it. Writing the outcome from a flow, for example after a classification step reads the reply, keeps inbox reporting accurate without manual triage.
Activity and Reporting
5- Get Sent Activity Returns the log of emails sent, with message, sequence, recipient and timestamp, filterable by sequence, recipient or time window.
- Get Opens Activity Returns the log of opens, each tied to the originating message, sequence and recipient. Opens are only recorded when open tracking was enabled on the sequence, which is worth checking before treating a zero as a signal.
- Get Clicks Activity Returns the log of link clicks with the same filters. Clicks are only recorded when click tracking was enabled on the sequence.
- Get Replies Activity Returns the log of replies received, each tied to the originating message, sequence and sender. Poll this on a schedule when a near-realtime reply feed is needed.
- Get Reports Returns workspace-level reports over a time window, optionally scoped to one team member. Use it for roll-up numbers across sequences rather than the per-sequence figures.
Senders and Templates
4- Get Senders Returns the sending mailboxes grouped by folder with id, address, display name, status and owner. Filter by folder, connection health, warm-up state, or whether a custom tracking domain is missing, which together make the standard pre-flight before a launch.
- Add Sender Connects an additional sending mailbox using SMTP and IMAP credentials. Google and Microsoft mailboxes are connected through OAuth in the SalesBlink app instead, so this action covers custom SMTP and IMAP only.
- Get Templates Returns the reusable email templates with subject line, body, folder, star and archive state, filterable by name, flags or owner.
- Create Template Creates a reusable template with subject and body, optionally filed, starred and given attachments. Templates hold the personalization placeholders that sequence steps expand per prospect.
Workspace
5- Get Folders Returns the folders used to organise lists, templates, sequences and senders. Folder ids are what the create actions expect when filing a new object.
- Create Folder Creates a folder for one class of object: lists, templates, sequences or email senders.
- Get Users Returns the users on the workspace with identity and role. Use it to resolve the owner email addresses that the list, sequence, sender and report filters expect.
- Add User Invites a user with a role of Client, User, Admin or Developer. The role governs what the invitee can see and change once they accept, so this is an access decision rather than a housekeeping one.
- Get Workspaces Returns the workspaces reachable with the configured key. Agencies running several clients use separate workspaces, each with its own lists, sequences and senders.
Frequently Asked Questions
What can FlowRunner do with SalesBlink?
FlowRunner agents can run Get Lists, Create List, and Get List in SalesBlink, plus 32 more actions.
Does connecting SalesBlink to FlowRunner require OAuth?
No. SalesBlink connects to FlowRunner with an API key, no OAuth flow required.
Can SalesBlink trigger a FlowRunner workflow automatically?
SalesBlink doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SalesBlink
$100 in credits. No card required. Connect in minutes.