Mockingbyrd
MessagingRead and act on SMS conversations in Mockingbyrd, an AI SMS platform for collecting and following up with leads. Agents work the routine replies and hand the thread to a person when it turns into a real negotiation.
What This Integration Enables
Mockingbyrd is the odd one out among FlowRunner's notification connectors, and the difference matters more than the action count. Everything else in this part of the catalog sends. Mockingbyrd holds a conversation. Leads reply, the AI agent answers, and four triggers fire back into your flow when a thread reaches a real outcome: a first response, a completed SMS conversation, a completed call link conversation, a completed phone call. Treat it as a two way system or you will build the wrong flow.
That two way shape is what makes the human-in-the-loop design interesting here. The connector gives an agent both halves of the handover: Set Conversation AI Handling turns the automated replies off without ending the thread, and Send Conversation Message puts a human's words into the same SMS conversation the lead has been having. The lead never sees a transfer. They see the conversation continue. Around that, agents push new contacts into lead sources the moment a form is submitted, create and control campaigns, and read the reporting surface, including List Link Clicks, which is the sharpest engagement signal on offer because a click inside an SMS thread is a person actively going somewhere.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Speed to lead measured in seconds
A form is submitted in HubSpot. The agent calls List Lead Sources to resolve the right source for that form, then Add Contacts To Lead Source with the phone number, name and company. The live campaign attached to that source picks the contact up and starts the SMS thread. Nobody had to be at their desk. When On First SMS Response fires, the agent writes the reply and its timestamp back to the HubSpot record so the rep opening the deal already knows the lead is engaged.
Closing the loop into the CRM
On SMS Conversation Complete fires with the AI summary, the final disposition and the full transcript. The agent writes all three to the contact record in Salesforce, attaches the tracked link clicks from List Link Clicks, and routes the record by disposition: qualified leads to the assigned rep, disqualified ones to a suppression list so the next campaign does not contact them again. The transcript stops being trapped in the SMS tool.
Guarding the quota before the campaign runs
A scheduled flow is about to launch an outbound campaign. Before Create Campaign, the agent reads Get Billing Status to see the plan limits and how much remains, and List Phone Numbers to confirm the campaign has a valid sending number in the right area code. If the remaining allowance would not cover the contact list, it does not launch a campaign that will die halfway through. It posts the shortfall to the sales operations channel with the numbers from Get Dashboard Summary and lets a person decide whether to trim the list or raise the plan.
Human-in-Loop Highlight
The moment worth designing for is the reply that turns a scripted follow up into a negotiation. A lead answers "can you do 15 percent off if we sign this week," and the AI agent, which was scripted to book meetings, now has an opinion about pricing. Nothing in the platform stops it. The connector, though, gives an agent the exact two moves needed to stop it: the flow reads the thread with Get Conversation Details, detects language that commits the company, and calls Set Conversation AI Handling with handling off so the AI falls silent without closing the conversation. Then it posts into the sales channel: "Lead at +1 512 555 0142 asked for 15 percent off in thread 8841. I have muted the AI. Transcript attached. Who takes this?" A rep replies through Send Conversation Message and the lead sees one continuous SMS thread. Two things on this connector cannot be walked back, and they sit right next to that decision: Delete Conversation permanently removes the thread and its history, and stopping a campaign through Set Campaign State cannot be undone. Neither belongs in an unattended branch.
Agent Capabilities
24 actionsWorkspace and Account
5- List Workspaces Lists every Mockingbyrd workspace the connected account can access, with each workspace UID and name. The one action that does not require a workspace to be configured, so it runs first during setup to find the UID everything else needs.
- Get Dashboard Summary Retrieves headline metrics for the workspace: total, answered, connected, compliant and converted calls, stored contact count, SMS sent, delivered, responses and conversions, plus the derived rates. Used for periodic reporting without pulling individual records.
- Get Billing Status Retrieves the current plan with its call and contact allowances, how much has been used and how much remains. Used to gate a flow before it launches a campaign that would exceed the remaining quota.
- List Phone Numbers Lists the voice numbers attached to the workspace in both E.164 and display form, with area code. Used to confirm which numbers a campaign can dial from before creating one.
- List Script Templates Lists the reusable AI script templates on the account with their full prompt text and active flag. Used to start a new campaign from an approved prompt rather than authoring one inside a flow.
Conversations
7- List Conversations Retrieves a paginated page of SMS conversations with optional search, date range, campaign filtering, sorting and a filter for whether the lead replied. Used to sweep for threads that need attention.
- Get Conversation Details Retrieves one conversation in full: status, phone numbers, AI summary, transcript, analysis data including disposition and redirection, the ordered message history and the owning campaign. The richest single read in the connector and the natural follow up to a trigger firing.
- Get Conversation Transcript Retrieves the conversation record with its transcript and AI summary but without the expanded per message history. Used when a flow only needs the narrative text, for example to write a note back to a CRM.
- Send Conversation Message Sends an SMS directly into an existing conversation, bypassing the AI agent so a human or an external system takes over the thread. Used as the second half of a handover, after AI handling has been switched off.
- Set Conversation AI Handling Turns the AI agent on or off for a single conversation. Used to hand a thread to a person without ending it, and to give control back once the human part is done.
- Complete Conversation Marks a conversation complete so Mockingbyrd stops further follow up or re-engagement attempts. Used once a downstream system has taken ownership, for example after a meeting is booked.
- Delete Conversation Permanently deletes a conversation and its message history from the workspace. This cannot be undone, so it belongs behind a retention policy and a person, not inside a cleanup loop.
Contacts and Lead Sources
4- List Contacts Retrieves a paginated page of stored contacts, optionally narrowed by a search term matched against phone, email, name and address at once. Used for reconciliation against a CRM.
- List Lead Sources Lists the lead sources in the workspace. A lead source UID doubles as the contact list identifier Create Campaign expects, so this is the lookup to run before wiring a campaign to a set of contacts.
- Create Lead Source Creates an integration lead source and returns its UID. Used to keep one source per inbound channel so contacts arriving from different forms stay separable in reporting.
- Add Contacts To Lead Source Adds one or more contacts, each with a phone number plus optional name, email, address and company. The speed to lead entry point: called the moment a form is submitted, so the campaign attached to that source picks the contact up.
Campaigns
6- Create Campaign Creates an SMS or voice campaign from a script template, a contact list and a sending number. Supports inbound and outbound direction, draft or live publishing, retry and calling window rules, do not contact days, re-engagement attempts, voicemail handling and call transfer. Supplying a test phone sends a single test instead of creating the campaign, which is the safe way to preview a script.
- List Campaigns Lists the campaigns in the workspace, optionally filtered by search term and archived state, with their configuration. Used to find the campaign a conversation belongs to.
- Get Campaign Retrieves a single campaign by UID with its full configuration, including retry and calling window settings. Used to confirm what a campaign will do before changing its state.
- Set Campaign State Pauses a running campaign, resumes a paused one, stops it permanently, archives it or restores it. Only running campaigns can be paused and only paused ones resumed, and stopping cannot be undone.
- Delete Campaign Permanently deletes a campaign from the workspace. Archiving is the reversible alternative when the record should be kept.
- Get Campaign Statistics Retrieves aggregate campaign performance: total, answered, successful and compliant calls, the answer, compliance and follow up conversion rates, and tracked link clicks. Used for scheduled reporting alongside Get Dashboard Summary.
Calls and Engagement
2- List Calls Retrieves a paginated page of call logs, filterable by date range, campaign, disposition, redirection, disconnection reason and contact validity. Each record carries the numbers, status, timings, duration, direction and disposition.
- List Link Clicks Retrieves clicks on the links sent inside SMS conversations, filterable by date range and campaign, each with destination URL, timestamp, visitor IP and the full conversation the link was sent in. The sharpest available signal that a lead is actually engaged.
Triggers
4 triggersEvent Triggers
4- On First SMS Response Fires the first time a lead replies to a Mockingbyrd SMS, once per conversation, carrying the customer number, the sending number and the campaign. The speed to lead hook: it marks the reply that turns a contact into an engaged lead, and it is the right place to alert a rep.
- On SMS Conversation Complete Fires when an SMS conversation is closed out, either by the AI satisfying its end condition or by the conversation being marked complete. Carries the AI summary, final disposition, full transcript and campaign and contact details, which makes it the natural point to write the outcome back to a CRM.
- On Call Link Conversation Complete Fires when a lead who received an SMS link followed it through to a completed call. Carries the summary, disposition, transcript and campaign details. Used to keep link driven call outcomes separable from ordinary SMS threads in reporting.
- On Phone Call Complete Fires when a voice call placed or received by a campaign ends, carrying the call summary, the disposition the AI assigned, the transcript and the contact details. Used to log the outcome or route a follow up the moment the call finishes.
Frequently Asked Questions
What can FlowRunner do with Mockingbyrd?
FlowRunner agents can run List Workspaces, Get Dashboard Summary, and Get Billing Status in Mockingbyrd, plus 21 more actions.
Does connecting Mockingbyrd to FlowRunner require OAuth?
No. Mockingbyrd connects to FlowRunner with an API key, no OAuth flow required.
Can Mockingbyrd trigger a FlowRunner workflow automatically?
Yes. Mockingbyrd supports 4 triggers that can start a FlowRunner workflow automatically.
Start building with Mockingbyrd
$100 in credits. No card required. Connect in minutes.