Vybit
MessagingTurn automation events into personalized push notifications with their own custom sound through Vybit. Agents make an alert recognizable without a person looking at the screen.
What This Integration Enables
Vybit's premise is that sound is the interface. Each vybit pairs a custom sound with a default message, image and link, and when it fires, every subscriber hears that sound. The point is not the notification. The point is that someone on a floor, in a truck, or with their hands full learns what happened without looking at anything. That is a genuinely different design target from every other push connector in this catalog, all of which assume the recipient will read the screen.
Agents get seven actions around that idea. Trigger Vybit fires as the owner, delivering to every subscriber, with the message, image and link overridable per trigger so one sound can carry different details each time. Create Vybit and Update Vybit let a flow build a temporary alert for an incident or a campaign and switch a noisy one off during a maintenance window without deleting it. List Notification Logs is the audit trail: what fired, when, who sent it, what the message said and any custom log text attached at trigger time. Get Usage Metrics reports notifications sent today and this month against the tier's daily, monthly and per vybit caps, which matters more here than on most connectors, because a trigger rejected for exceeding a cap does not ring. A missing sound is indistinguishable from nothing happening.
Without FlowRunner
With FlowRunner
Use Case Scenarios
An audible severity ladder for production
Three vybits exist, each with its own sound: one for a failed job, one for an error rate spike, one for a full outage. When an incident opens in Sentry, the agent classifies severity and triggers the matching vybit, overriding the message with the service name and the error count and the link with a direct URL to the issue. The on-call engineer knows the severity from the doorway. They open the phone only for the ones that earned it.
A vybit that exists only for as long as the incident does
A major migration is scheduled and needs its own alert stream that does not exist afterwards. The agent calls Create Vybit with a distinct sound, posts the returned subscription key into the migration channel so the team can subscribe, and fires it through the cutover. When the migration closes, a cleanup flow calls Delete Vybit. Everything created for the incident goes away with the incident rather than becoming another sound nobody remembers the meaning of.
Silence with an end date
Planned maintenance will make a monitored service throw errors for two hours. Rather than letting a vybit fire fifty times and train everyone to ignore it, the agent calls Update Vybit to set the status to off at the start of the window and back on at the end. Trigger Vybit against a vybit with status off succeeds and reports that nothing was sent, so anything the flow fires during the window still lands in the notification logs even though nobody hears it. The record exists. The noise does not.
Human-in-Loop Highlight
The value of this connector is a trained reflex, and trained reflexes are exactly what an automation can destroy without producing a single error. Once a shift has learned that the rising three tone means the line stopped, that sound is doing real work. Now consider Update Vybit swapping the sound on that vybit, or Create Vybit claiming it for something else, since each sound can only be attached to one vybit at a time. Nothing fails. No exception is raised. The alert fires perfectly and the people who were trained on it do not react, or react to the wrong thing. Delete Vybit is worse in the same direction: it permanently removes the vybit along with its subscriptions and QR codes, the webhook trigger key stops working, and no subscriber is told their phone just went quiet. So an agent is free to fire vybits, to override messages, and to switch a vybit off and on for a maintenance window, all unattended. Before it reassigns a sound or deletes a vybit, it pulls List Notification Logs for that vybit and stops: "This vybit fired 34 times in the last 30 days and has active subscribers. Reassigning its sound to the new deploy alert will break what those people are trained to hear. Reassign, pick an unused sound, or leave it?" The operations lead answers. This is the digital andon cord pointed back at the alerting system itself, which is the one place teams usually forget to point it.
Agent Capabilities
7 actionsNotifications
2- Trigger Vybit Fires a vybit as its owner, delivering a push notification with its custom sound to every subscriber. The configured message, image and link are used by default and can be overridden per trigger, and an optional log entry can be attached for auditing. Subject to the daily and monthly caps of the account tier. When the vybit's status is off, the call succeeds and reports that nothing was sent.
- List Notification Logs Retrieves the notification history for the account: which vybit fired, when, who sent it, the message delivered and any custom log text attached at trigger time. Supply a vybit to restrict the history to that vybit, or omit it to return logs across every vybit you own and follow. The audit surface, and the evidence a person needs before changing a sound people rely on.
Vybits
4- List Vybits Retrieves the vybits owned by the account, including each vybit's key, sound, trigger type, status, default message and webhook trigger key, with free text search and pagination. Used to discover the vybit key that the trigger, update and delete actions require.
- Create Vybit Creates a new vybit and returns it with the generated key, webhook trigger key and subscription key. A vybit pairs a custom sound with a default message, image and link, and can be fired by an incoming webhook, a cron schedule, a geofence, an integration or one off reminders. Each sound can only be attached to one vybit at a time, so creating one can take a sound away from an existing alert.
- Update Vybit Applies a partial update, changing only the fields supplied. Used to switch a vybit on or off from a flow during a maintenance window, swap its sound, or rewrite the default message, image and link subscribers receive.
- Delete Vybit Permanently deletes a vybit owned by the account. All associated data including subscriptions and QR codes is removed and the webhook trigger key stops working, while previously recorded notification logs are retained. This cannot be undone, and subscribers are not notified that their alert has gone.
Account
1- Get Usage Metrics Reports notification usage and capacity for the account: notifications sent today and this month, the number of vybits created, the daily, monthly and per vybit caps of the current tier, and the date the monthly counter resets. Used to guard a batch against the tier limits that cause triggers to be rejected, because a rejected trigger makes no sound at all.
Frequently Asked Questions
What can FlowRunner do with Vybit?
FlowRunner agents can run Trigger Vybit, List Vybits, and Create Vybit in Vybit, plus 4 more actions.
Does connecting Vybit to FlowRunner require OAuth?
No. Vybit connects to FlowRunner with an API key, no OAuth flow required.
Can Vybit trigger a FlowRunner workflow automatically?
Vybit doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Vybit
$100 in credits. No card required. Connect in minutes.