Slybroadcast
Voice & TelephonySend ringless voicemail campaigns through Slybroadcast, delivering pre-recorded audio straight to voicemail boxes. Agents reach a list without ringing a phone, and hold the send behind an approval.
What This Integration Enables
Slybroadcast delivers ringless voicemail, and that phrase deserves to be taken literally rather than treated as a delivery detail. The audio lands in a recipient's voicemail box without their phone ringing. Nobody is interrupted, nobody declines the call, and nobody gets the chance to. That is a genuinely different consent posture from placing a call, and it is the reason this connector's design puts the Do Not Dial list, the message balance and the audio library one step in front of the send rather than one step behind it.
FlowRunner agents work every part of that sequence. They maintain suppression by adding and removing numbers on the account's Do Not Dial list in submissions of up to 10,000. They resolve the right recording from the audio library by its self-created title and duration, or point at a file hosted on your own site in WAV, MP3 or M4A. They schedule delivery in US Eastern Time on a 24-hour clock or send immediately, and they read per-number results back with the delivery status, the carrier and the reason for failure. What they do not do is submit the campaign on their own. The send is where a person signs, because a voicemail already sitting in someone's box cannot be recalled by any action in this list.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A reminder that arrives without interrupting anyone
Appointment and payment reminders are the natural fit for ringless voicemail, because the recipient gets the information at the moment they choose to check their messages rather than at the moment you chose to dial. The agent assembles tomorrow's list from the scheduling system, scrubs it against Do Not Dial, and schedules Send Campaign with Account Audio for a specific Eastern Time window. Because scheduling is separate from sending, Cancel Campaign remains available right up until the campaign starts, so a clinic that closes for weather can pull the whole run back. Once it is running, Pause Campaign and Resume Campaign handle a temporary hold, and Stop Campaign ends it permanently, since a stopped campaign cannot be resumed.
Undelivered numbers routed somewhere they will actually land
A campaign completes and the interesting half of the result is the failures. Get Campaign Results returns one row per destination with the delivery status, the reason for failure where applicable, the delivery time and the carrier. The agent splits that: delivered numbers are logged against the CRM record, and failures are grouped by carrier reason. Numbers that failed for a reason that will not resolve on retry are handed to ClickSend or Twilio as an SMS follow-up instead, and the pattern is reported so a systematic carrier problem shows up as one alert rather than as 400 individual failures nobody read.
Suppression that is asymmetric on purpose
Adding someone to the Do Not Dial list and taking them off it are not mirror-image operations, and the flow should not treat them as such. When an opt-out arrives from any channel, the agent runs Add to Do Not Dial List immediately and without asking, because honoring a stop request instantly is always correct. Removing someone is the opposite. Remove from Do Not Dial List puts a person who previously opted out back into the addressable audience, so the agent will not run it from an automated signal at all. It routes the request to a named owner with the original opt-out date and the source attached, and waits. Suppression is one of the few places where the asymmetry between two adjacent actions is the whole design.
Human-in-Loop Highlight
Send Campaign with Account Audio is the point of no return, and the specific hazard is smaller and stupider than most people expect. The audio is referenced by its self-created name, and that name is case sensitive. "SpringPromo" and "springpromo" are not the same file. A campaign can therefore go out with last quarter's recording, or the wrong client's recording, and everything about the request will have looked correct. Meanwhile the delivery itself is one-way: Stop Campaign halts what has not yet gone out and cannot be resumed, but every voicemail already deposited stays deposited. There is no recall in this connector, because there is no recall in the medium.
So the agent does all the preparation and hands over one clear question. It posts to the campaign owner: "Campaign ready for the 10:00 Eastern window. Audio file 'Q3_Renewal_Reminder_v2', 31 seconds, uploaded 14 July. Audience is 3,180 numbers after removing 212 on the Do Not Dial list. Message balance covers it with 1,140 credits remaining after 400 pending sends. Confirm this is the right recording and send?" The owner listens to the file if they are not certain, corrects the audience if the segment was wrong, and approves. Only then does the agent submit. This is human-in-the-loop placed where irreversibility actually lives, and it costs the owner about fifteen seconds against a send that cannot be undone.
Agent Capabilities
19 actionsCampaigns
11- Send Campaign with Account Audio Submits a ringless voicemail campaign using an audio file stored in the account, referenced by its self-created name, which is case sensitive, or by its system file name. Destinations are given as phone numbers, up to 10,000 per submission, or as a stored phone list ID. Delivery is scheduled in US Eastern Time on a 24-hour clock, or sent immediately. Returns the session ID assigned to the campaign.
- Send Campaign with Audio URL Submits a campaign using audio hosted at an external URL. The file must be WAV, MP3 or M4A and longer than five seconds. Destinations and scheduling work as they do for account audio, and the session ID is returned the same way.
- Get Campaign Results Returns the call results of a campaign by session ID. Each row carries the destination number, the delivery status, the reason for failure where applicable, the delivery time and the carrier.
- Get Call Status Returns the delivery status of a single number within a campaign, including delivery time, carrier and failure reason. Used to answer a question about one recipient without pulling the whole result set.
- List Campaigns Returns the session IDs and creation timestamps of campaigns on the account, covering campaigns sent in the last 24 hours and campaigns scheduled up to 90 days ahead.
- List Campaigns by Date Returns the campaigns sent on a specific date, and an empty list when none match. Used for daily reporting.
- Get Campaign Title Returns the title of a campaign by session ID. Used to label a result set with something a person recognises.
- Pause Campaign Temporarily pauses a running campaign without cancelling it, so it can be resumed later.
- Resume Campaign Resumes a paused campaign.
- Stop Campaign Stops a campaign that is currently running. A stopped campaign cannot be resumed, and messages already delivered are unaffected.
- Cancel Campaign Cancels a scheduled campaign that has not started running yet. This is the action that gives a scheduled send a real window in which it can still be pulled back.
Audio Files
3- List Audio Files Returns all audio stored in the account with the system file name, the self-created title and the creation date, optionally including each file's duration in seconds. The duration is what lets an approver confirm they are signing off on the right recording.
- Delete Audio File Deletes an audio file from the account by its system file name. Used to retire a recording once campaigns referencing it have completed.
- Download Audio File Downloads a file created with the Slybroadcast Recording Center by its 5-digit audio code and saves it to FlowRunner file storage, returning the stored URL and path. Used to archive a recording alongside the campaign it belongs to.
Phone Lists
1- List Phone Lists Returns the phone lists stored in the account. A list ID can be used to address a stored list when sending, instead of passing numbers directly.
Do Not Dial
2- Add to Do Not Dial List Adds numbers to the account's Do Not Dial list so they receive no voice messages from the account. Up to 10,000 numbers per submission. Flows run this immediately on any opt-out signal.
- Remove from Do Not Dial List Removes numbers from the Do Not Dial list, returning them to the addressable audience. Up to 10,000 numbers per submission. Flows route this to a person rather than triggering it from an automated signal.
Account
2- Verify Credentials Verifies that the configured account email and password are accepted by the Slybroadcast gateway. Used as a connection check before a campaign flow runs.
- Get Message Balance Returns the remaining message credits and the number of pending messages already scheduled. Both numbers matter, because a balance that covers a list today may not cover it once pending sends land.
Triggers
1 triggersEvent Triggers
1- On New Campaign Fires when a new campaign appears on the account, covering campaigns sent within the last 24 hours and campaigns scheduled up to 90 days ahead. The first run records a baseline and emits nothing, after which each newly seen campaign fires once, deduplicated by session ID. Used to start downstream reporting whenever a campaign is created, including ones submitted from the Slybroadcast dashboard rather than from a flow.
Frequently Asked Questions
What can FlowRunner do with Slybroadcast?
FlowRunner agents can run Send Campaign with Account Audio, Send Campaign with Audio URL, and Get Campaign Results in Slybroadcast, plus 16 more actions.
Does connecting Slybroadcast to FlowRunner require OAuth?
No. Slybroadcast connects to FlowRunner with an API key, no OAuth flow required.
Can Slybroadcast trigger a FlowRunner workflow automatically?
Yes. Slybroadcast supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Slybroadcast
$100 in credits. No card required. Connect in minutes.