SalesTrigger
Sales OutreachBuild multi-step LinkedIn connection and message sequences with the SalesTrigger OutReach API and enrol leads in them. Agents pace outreach and route replies to the right owner.
What This Integration Enables
Most LinkedIn outreach tools treat the reply as an exit: the sequence ends, the notification fires, and a human takes over from a cold start. SalesTrigger builds the other half out properly. Get Pending Reply Leads gives an agent the queue of warm conversations waiting on an answer, Get Reply Suggestions produces a draft grounded in the thread, and Send Auto Reply delivers it. The vendor documents both paths for that draft, sending it directly or routing it for approval first, which is an unusually honest acknowledgement that the second path exists for a reason. It is also the exact shape FlowRunner is built for.
Around the reply loop, agents get the full campaign surface: create a sequence as an ordered chain of connection requests and follow-ups with per-step delays, add leads individually or as an audience with up to five personalization fields each, pause and reactivate, and read execution logs when a sequence stalls. Because SalesTrigger also holds its own saved prospect searches, sourcing and outreach close into one loop that never leaves the flow. FlowRunner's connectors expose all of it, and FlowRunner's contribution is the part the tool cannot supply on its own: knowing which of those warm replies an agent is allowed to answer.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Warm reply triage in minutes, not days
The reply trigger fires. The agent reads the whole exchange with Get Conversation Messages so it is judging the reply in context rather than in isolation, requests a draft with Get Reply Suggestions, and classifies the intent. Clear scheduling requests are pushed straight into Calendly booking and the draft is offered to the rep with the link already embedded. Clear questions about pricing or scope are drafted and offered for approval. Anything reading as a deferral or a removal is routed to the rep without a draft at all. Once the flow has handled the thread, it calls Mark Conversation Read so unread-based monitoring does not replay the same conversation on the next poll.
Sourced prospects into live outreach without an export
A weekly flow calls List Sales Trigger Searches to find the most recent saved prospect search, pulls the matched people with Get Sales Trigger Search Leads, and checks each against HubSpot so anyone with an open opportunity or an existing owner is removed. What survives goes into Create Audience in a single call rather than one request per prospect. The list never lands in a spreadsheet, which means it never goes stale between the search and the send.
Catching a stalled sequence before the week is lost
A scheduled flow reads Get Campaign Logs for each active campaign and looks for the failure patterns that matter, principally a sending account that has hit a weekly invitation limit or lost its session. It cross-checks List LinkedIn Accounts for connection health, and when an account reports disconnected or expired cookies it calls Set Campaign Status to pause the affected campaigns rather than letting them burn through a week of silent failures. The rep gets a message naming the account, the campaigns it stopped and what to reconnect.
Human-in-Loop Highlight
Get Pending Reply Leads returns every lead who replied. Not every interested lead: every lead. The prospect who asked for pricing, the prospect who said "not now, try me in Q4", and the prospect who wrote "please remove me" are all in the same queue. Send Auto Reply will cheerfully deliver an AI-drafted answer to any of them, into a live LinkedIn thread, under a named rep's own identity, with no way to unsend it. A confident automated rebuttal to a removal request is not a bad email. It is the one outcome that costs the rep the relationship and, at volume, the account. So the classification step never gets to be the last word. The agent puts the prospect's exact words next to its proposed draft and asks the rep who owns the conversation: "Reply from Devon Marsh at Northwind: 'Not the right time, and please take me off this.' Draft suggests a Q4 follow-up. Send, edit, or stop outreach to this lead?" The rep decides. That is what a digital andon cord is for: the machine keeps the line moving and stops it when the next move is not obviously safe.
Agent Capabilities
24 actionsCampaigns
10- Create Campaign Creates a LinkedIn outreach campaign against a connected account. The sequence is an ordered chain of steps, each either a connection request or a follow-up message, carrying its own template and an optional delay after the previous step. Leads are supplied as profile URLs with up to five custom fields for personalization placeholders.
- List Campaigns Returns the campaigns on the account, filtered by mode so a flow can list classic outreach campaigns or AI SDR campaigns. An API-only switch narrows the result to campaigns created through the API rather than in the SalesTrigger interface.
- Get Campaign Analytics Returns performance analytics over a chosen window, from today through the trailing three months. Used to feed a scheduled digest or a dashboard without exporting anything.
- Set Campaign Status Pauses or reactivates a campaign. Pausing halts further invitations and messages while preserving progress, which makes it the correct response to a holiday period, a copy revision or a disconnected sending account.
- Delete Campaign Permanently deletes a campaign and its scheduled outreach. This cannot be undone, so pause instead whenever the stop is temporary.
- Get Campaign Leads Returns every lead enrolled in a campaign with its position in the sequence and outreach status, such as pending, connection sent, connection accepted, replied or failed. This is the primary way to sync outreach progress back onto CRM records.
- Get Campaign Conversations Returns the conversations a campaign generated for one connected sending account. Because a campaign can run from several accounts, the account identifier is required so the right mailbox is read.
- Get Campaign Logs Returns the execution log for a campaign, recording each attempted action and any error. Used to diagnose why a sequence stalled, for example when an account has hit a weekly invitation limit.
- Get Campaign Sequence Settings Returns the configured sequence: each step, its type, its message template and the delay applied after the previous step. Read this before editing messages so existing chain positions are preserved.
- Edit Campaign Messages Replaces the message chain of an existing campaign so copy can be revised without rebuilding it or re-uploading leads. The submitted chain replaces the stored one outright, so supply every step including position and type.
Leads and Audiences
3- Add Lead To Campaign Adds a single lead to a running campaign by profile URL, with up to five custom fields available as personalization placeholders. This is the natural bridge from a form submission or a CRM stage change into live outreach.
- List Available Audiences Returns the audiences that can be attached to a campaign. An audience is a saved batch of leads, so this is the first step when adding an existing cohort rather than enrolling one person at a time.
- Create Audience Creates a new audience on a campaign, enrolling a batch of profiles in one call. Prefer this over per-lead adds when importing a list, since it avoids one request per prospect.
Reply Handling
4- Get Pending Reply Leads Returns the leads on a campaign who have replied and are waiting for a response. This is the warm queue, and it contains every reply regardless of sentiment, so a flow should classify before it acts.
- Get Reply Suggestions Returns AI-generated reply suggestions for a lead who has responded. The draft is a starting point for a person, or an input to an approval step, depending on how much the conversation is worth.
- Send Auto Reply Sends a reply to a lead in a campaign conversation. Pair it with the suggestions action to deliver a drafted answer, ideally after a human has read what the prospect actually wrote.
- Get Auto Reply Settings Returns the automatic reply configuration for a campaign, showing whether AI replies are enabled and how they are constrained. Read it before changing automation behaviour so the existing posture is understood.
Inbox
4- List Inbox Conversations Returns every conversation across the account's connected sending accounts, with an option to show only threads carrying unread messages. This is the account-wide view, as opposed to the campaign-scoped conversation list.
- Get Conversation Messages Returns the full message history of one conversation in chronological order. Used to give a classification or drafting step the complete context of a thread rather than the last message alone.
- Send Conversation Message Sends a new message into an existing conversation from a specified connected account. Unlike the auto reply action this works on any thread in the inbox, not only those tied to a campaign's pending replies.
- Mark Conversation Read Clears a conversation's unread flag. Call it at the end of a flow that has processed a reply so unread-based monitoring does not pick the same thread up again.
Account and Lead Sourcing
3- List LinkedIn Accounts Returns the connected LinkedIn accounts with their connection health, reporting whether each is connected, disconnected or holding expired cookies. Check this before launching, because outreach from a stale account fails silently.
- List Sales Trigger Searches Returns the most recent saved prospect searches on the account. Each search represents a set of matched people, and its identifier is what the lead retrieval action needs.
- Get Sales Trigger Search Leads Returns the prospects matched by a saved search. Chain it with the campaign or audience actions to push freshly sourced leads straight into outreach without an export step in the middle.
Triggers
1 triggersEvent Triggers
1- On New Conversation Reply Fires when a prospect replies on LinkedIn, emitting the conversation record so a flow can fetch the thread and draft a response. Detection is based on the account-wide unread conversation list, which has two practical consequences worth designing around: mark a conversation as read once it is handled or the trigger will fire on it again, and expect the first poll to establish a baseline without firing so existing unread threads are not replayed. The polling interval is configurable down to thirty seconds, so warm replies can be in front of a rep within a minute of arriving.
Frequently Asked Questions
What can FlowRunner do with SalesTrigger?
FlowRunner agents can run Create Campaign, List Campaigns, and Get Campaign Analytics in SalesTrigger, plus 21 more actions.
Does connecting SalesTrigger to FlowRunner require OAuth?
No. SalesTrigger connects to FlowRunner with an API key, no OAuth flow required.
Can SalesTrigger trigger a FlowRunner workflow automatically?
Yes. SalesTrigger supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with SalesTrigger
$100 in credits. No card required. Connect in minutes.