DEV Community: Vybit

A Cash Register for Every Stripe Payment, a Horn for Every Failed One

Vybit — Mon, 09 Nov 2026 15:37:46 +0000

Stripe will email you about payments, and the Stripe app can push a notification, but that reaches whoever is signed in to the dashboard and sounds like everything else on the phone. A failed payment is worse: it sits quietly in a list until someone goes looking, and by then the customer has gone.

You can fix both with two vybits and Stripe's own webhook settings. No Zap, no code, no server. Here is what it sounds like.

Play the interactive demo on the original post.

What you will hear

A cash register on every subscribed phone the moment a payment succeeds, reading "New Stripe payment". A car horn the moment one fails, reading "A Stripe payment failed". Two different sounds, so the whole team knows which one it is without picking up the phone. Pick any sounds you like, or record your own.

Step 1: make two vybits

Sign in to Vybit and create a vybit called "Payment received". Set the default message to "New Stripe payment" and choose a cash register sound.
Create a second vybit called "Payment failed", with the default message "A Stripe payment failed" and a sound nobody will mistake for good news (a horn works well).
Leave the trigger type of both as Webhook.
Copy each vybit's trigger URL. It looks like https://vybit.net/trigger/abc123xyz.
Share each vybit with your team. New vybits start out private, so either invite people by email (open the vybit, click PEEPS, enter their email and click INVITE), or set the vybit's subscription access to unlisted and share its subscribe link. Everyone who should hear payments signs in with a free Vybit account and subscribes. The failed-payment vybit might go to fewer people: whoever follows up with customers.

That card belongs to a real demo vybit, so go ahead and scan the code to see what subscribing looks like. The vybit is switched off and we never send to it.

Step 2: point Stripe at them (Stripe's own settings)

Menu path checked November 8, 2026, in the Stripe Dashboard.

In the Stripe Dashboard, open Workbench and go to the Webhooks tab.
Click Add destination.
Keep Your account selected, leave the payload style on Snapshot, and keep the suggested API version.
Under Events, search for payment_intent.succeeded, tick it, then click Continue.
Choose Webhook endpoint and click Continue.
Name the destination (for example "Vybit cash register"), paste the "Payment received" trigger URL as the Endpoint URL, and add a description if you like.
Click Create destination.

Then do it once more for the horn: a second destination with the event payment_intent.payment_failed and the "Payment failed" trigger URL.

That covers Checkout, Payment Links, invoices and subscription renewals, because all of them take the money through a payment intent.

A few things worth knowing:

Try it in test mode first. Build the two destinations in a sandbox or test mode, pay with Stripe's test card 4242 4242 4242 4242 to hear the register, and with the declining test card 4000 0000 0000 0002 to hear the horn. Or skip the test cards: open each test destination in Workbench, click Send events, and pick its event (payment_intent.succeeded for the register, payment_intent.payment_failed for the horn). Stripe sends a sample event straight to the trigger URL. Then create the same two destinations in live mode. Test and live destinations are separate, so nothing rings for real payments until you add the live ones.
Vybit uses its default message. Stripe sends the whole event to the trigger URL. Vybit rings the vybit with its default message and does not read the amount out of a Stripe event. If you want "Payment: $49.00" on the lock screen, use the automation-platform variant below.
Stripe's signature is not needed. Stripe signs every event; the trigger URL does not check signatures, so there is nothing to configure. Keep each trigger URL private, since anyone who has it can ring that vybit.
Turning a vybit off is safe. Stripe still gets a success reply and nothing rings. If you delete a vybit instead, Stripe sees errors, retries for a while, and may eventually disable the destination and email you about it. You can see every attempt under the destination's Event deliveries tab.

Step 1 and 2, the AI way: copy this prompt

If your AI assistant is connected to the Vybit MCP server (https://api.vybit.net/v1/mcp; setup steps for Claude, ChatGPT, Gemini, Grok, Mistral Vibe, Perplexity and Muse in our AI assistant guide), paste this into a new chat and change the parts in brackets:

Use my Vybit connector to set up payment alerts for my Stripe account.

1. Create a private vybit called "[Payment received]" with the default
   message "[New Stripe payment]". Search the Vybit sounds for
   "cash register", show me the three best matches with their play
   links, and use the one I pick.
2. Create a private vybit called "[Payment failed]" with the default
   message "[A Stripe payment failed]". Search the sounds for "horn"
   and let me pick again.
3. Invite these people to subscribe to "Payment received" by email:
   [alex@example.com, sam@example.com]
   and only these to "Payment failed": [sam@example.com]
4. Give me each vybit's trigger URL (https://vybit.net/trigger/
   followed by its trigger key) so I can paste them into Stripe.
5. Send one test of each with the message "Test: if you heard this,
   payment alerts work".

Then paste the two trigger URLs into Stripe as in Step 2. Your assistant handles the Vybit side; the two Stripe destinations take a minute in the Dashboard.

Variant: put the amount in the notification

If you want the amount and customer on the lock screen, or a grander sound for big payments, route the event through an automation platform. Vybit is an official app on Zapier, Make and IFTTT, with a verified community node for n8n.

Start from the platform's Stripe trigger for a new payment (or a failed one).
Add the Vybit action that triggers your vybit, and fill the message from the payment, for example "Payment: {{amount}} {{currency}}".
Stripe reports amounts in the smallest unit (cents for dollars), so 4900 means $49.00. Most platforms have a formatter step to divide by 100.
Add a filter on the amount if you want a separate fanfare vybit for big payments. Our post A Grander Bell for a Bigger Sale walks through that pattern step by step.

If you post to a trigger URL yourself, a JSON body with a message field, such as {"message": "Payment: $49.00"}, replaces the default message for that one alert.

How counting works

One notification is one vybit reaching one person, on all of their devices, and that includes you. A payment that rings you and 4 teammates uses 5 notifications. Subscribers are free and unlimited; nobody needs a seat to listen.

Some realistic businesses:

Just you, about 30 payments a day: 30 x 1 x 31 = 930 notifications a month.
You and 4 teammates, about 15 payments a day, with failed payments (about 1 a day) going to 2 of you: (15 x 5 + 1 x 2) x 31 = 2,387 a month.
A team of 8, about 50 payments a day: 50 x 8 x 31 = 12,400 a month.

Which plan fits

Free fits a solo business: 1,500 notifications a month, up to 100 in a day.
Pro fits you and 4 teammates: 3,000 notifications a month and 3 manager seats.
Team fits the team of 8 doing 50 payments a day: 15,000 notifications a month and 20 manager seats.

Manager seats are only for people who help you run the account. Everyone who just needs to hear the register subscribes for free. The pricing page has the full comparison, and if you need more than Business offers, write to plans@vybit.net.

Originally published on Signals, the Vybit blog.

New Lead? Ring the Whole Sales Floor

Vybit — Wed, 28 Oct 2026 15:58:45 +0000

A new lead fills in your contact form, the form sends an email, and the email lands in a shared inbox next to forty newsletters. The fastest reply usually wins the deal, and nobody on the team knew the lead was there.

You can give every new lead its own sound on everyone's phone. The simplest version needs nothing but your own web form and one vybit.

What you will hear

A ship's bell (or any sound you choose) on every phone subscribed to the vybit, the moment someone submits your form. The lock screen shows who it is, for example "New lead: Jane Doe, wants a quote". The whole sales floor hears the same bell, so whoever is free grabs it.

Step 1: make the vybit

Sign in to Vybit and create a vybit called "New lead". Set the default message to "New lead from the website" and pick a sound your team will learn fast.
Leave the trigger type as Webhook.
Copy the vybit's trigger URL. It looks like https://vybit.net/trigger/abc123xyz.
Share the vybit's subscribe link with your sales team. Each person signs in with a free Vybit account and subscribes. Listening is free; nobody needs a manager seat to hear the bell.

Step 2: ring it from your website's form

If your site has an HTML form, add a few lines of script so the form also sends one alert to the trigger URL. The trigger URL accepts a normal form post or JSON, and a field called message becomes the text on the lock screen.

Here is a complete example. Replace the trigger URL with yours, and keep whatever your form already does.

<form id="lead-form">
  <input name="name" placeholder="Your name" required>
  <input name="email" type="email" placeholder="Email" required>
  <textarea name="note" placeholder="What can we help with?"></textarea>
  <button type="submit">Send</button>
</form>

<script>
  document.getElementById("lead-form").addEventListener("submit", function (e) {
    e.preventDefault();
    var f = e.target;
    var text = "New lead: " + f.elements["name"].value +
      " (" + f.elements["email"].value + ")";
    fetch("https://vybit.net/trigger/abc123xyz", {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({ message: text.slice(0, 200) })
    }).finally(function () {
      f.reset();
      alert("Thanks, we will be in touch shortly.");
    });
  });
</script>

A few things worth knowing:

No server needed. The trigger URL allows calls from any website, so this runs straight from the visitor's browser.
Keep the alert short. Put the name and one detail in the message. The full lead still goes wherever your form sends it today (your inbox or CRM); the vybit is the bell, not the record.
The URL is visible in your page source. Anyone who reads it could ring your vybit. For most small sites that is fine. If spam becomes a problem, turn the vybit off for a while (nothing rings and the form still works), or send the alert from your form service's webhook setting instead, so the trigger URL never appears in the page.
Form builders work too. Many form tools have a "webhook on submission" setting. Paste the trigger URL there. If the tool lets you choose the fields it sends, send one called message; otherwise the vybit rings with its default message.

HubSpot and Freshdesk: their own webhook settings

These two paths are written from each tool's own documentation (checked October 20, 2026). We have not run them end to end yet, so check the first alert before you rely on it.

HubSpot (the "Send a webhook" workflow action needs Data Hub Professional or Enterprise):

Go to Automation > Workflows and create a contact-based workflow that enrolls contacts when, for example, a form is submitted or the lifecycle stage becomes Lead.
Click the + icon to add an action and choose Send a webhook under Data ops.
Choose POST and paste your trigger URL.
Select Customize request body and add one static value named message, such as "New HubSpot lead". Without it, HubSpot sends the whole contact record and the vybit rings with its default message.
Save the action and turn the workflow on.

Freshdesk (for leads that arrive as tickets, such as a "Talk to sales" form or email address):

Go to Admin > Workflows > Automations (in Freshdesk Omni: Admin Settings > Configuration and Workflows > Ticket Automations).
On the Ticket Creation tab, click New Rule and add a condition that matches your sales tickets, for example the group or the email address they arrive at.
Under actions, choose Trigger webhook, set the request type to POST and paste your trigger URL.
Choose JSON encoding and Advanced Content, and enter a body such as {"message": "New sales ticket: {{ticket.subject}}"} using Freshdesk's placeholder for the subject.
Click Preview and Save, then turn the rule on.

Webhook actions in both tools depend on your plan, so check yours before you start.

Step 1 and 2, the AI way: copy this prompt

If your AI assistant is connected to the Vybit MCP server (https://api.vybit.net/v1/mcp; setup steps in our AI assistant guide), paste this into a new chat and change the parts in brackets:

Use my Vybit connector to set up a new-lead alert for my sales team.

1. Create a private vybit called "[New lead]" with the default message
   "[New lead from the website]". Search the Vybit sounds for "bell",
   show me the three best matches with their play links, and use the
   one I pick.
2. Invite these people to subscribe by email:
   [alex@example.com, sam@example.com, priya@example.com]
3. Give me the vybit's trigger URL (https://vybit.net/trigger/ followed
   by its trigger key).
4. Write the script for my contact form so each submission also posts
   {"message": "New lead: <name> (<email>)"} to that trigger URL. My
   form's fields are named [name] and [email].
5. Send one test with the message "Test: if you heard this, lead
   alerts work".

Your assistant sets up the Vybit side and hands you the form script; you paste it into your site.

Variant: an automation platform

If your leads already flow through Zapier, Make, IFTTT or n8n, add the Vybit action to that flow instead. Vybit is an official app on Zapier, Make and IFTTT, with a community node for n8n.

Start from your lead source's trigger (a new form submission, a new CRM contact, a new ticket).
Add the Vybit action that triggers your vybit, and fill the message from the lead, for example "New lead: {{name}}, {{company}}".
Add a filter if only some leads should ring, such as a minimum deal size or one region.

How counting works

One notification is one vybit reaching one person, on all of their devices. A lead that rings 5 people on the sales floor uses 5 notifications. Subscribers are free and unlimited.

Some realistic teams:

Just you, about 5 leads a day: 5 x 1 x 31 = 155 notifications a month.
A sales team of 5, about 10 leads a day: 10 x 5 x 31 = 1,550 a month.
A sales floor of 12, about 25 leads a day: 25 x 12 x 31 = 9,300 a month.

Which plan fits

Free fits a solo founder: 1,500 notifications a month, up to 100 in a day.
Pro fits the sales team of 5: 3,000 notifications a month and 3 manager seats.
Team fits the sales floor of 12: 15,000 notifications a month and 20 manager seats.

Manager seats are only for people who help you run the account. Everyone who just needs to hear the bell subscribes for free. The pricing page has the full comparison, and if you need more than Business offers, write to plans@vybit.net.

Originally published on Signals, the Vybit blog.

Ask Your AI Assistant to Set Up Your Team's Alert Sounds

Vybit — Wed, 21 Oct 2026 15:58:59 +0000

Setting up a team alert usually means a settings page, a sound library, a list of email addresses and a webhook field in some other tool, all open in different tabs. With Vybit connected to your AI assistant, you describe the alert once in plain words and the assistant does the clicking for you.

What you will hear

A bell on every phone on your team, the moment something needs a person. In our test we asked for a front desk bell: a vybit called "Front desk bell" with a receptionist's bell ringing eight times and the message "Someone needs help at the front desk." Once it existed, the assistant fired a test from the chat, and then we fired it again from its trigger URL the way a webhook would. Both rang the same bell. You will pick your own sound, of course: a cash register for sales, a ship's bell for a new lead, something unmistakable for "the site is down."

Step 1: connect Vybit to your assistant (once)

Vybit runs a hosted MCP server at https://api.vybit.net/v1/mcp. MCP is the standard way AI assistants connect to outside tools. You add it once, sign in with your Vybit account, and from then on any chat can manage your vybits.

Claude (claude.ai or the Claude desktop app), Free, Pro and Max plans

In any chat, click the + button, choose Add connector, then Add custom connector. (You can also get there from Customize, then Connectors.)
Name it Vybit, enter the URL https://api.vybit.net/v1/mcp and click Continue.
Leave the default sign-in settings as they are and click Add.
Sign in to Vybit when asked and click Allow.
The first time Claude uses each Vybit tool, such as creating or sending a vybit, it asks you first. Approve it, or choose Always allow for the tools you are comfortable with.

Prefer to watch? Here is the whole Claude setup in four minutes, from adding the connector to hearing the first test vybit.

If a later chat does not seem to know about Vybit, open the + menu, then Connectors, and make sure Vybit is switched on.

On Claude Team and Enterprise, an owner adds it once under Organization settings, Connectors, Add, Custom, and each member then clicks Connect on it.

ChatGPT (chatgpt.com on the web), Plus, Pro, Business, Enterprise and Education plans

Open Plugins at chatgpt.com/plugins.
Click Add, then Add custom MCP server.
Name it Vybit, enter the Server URL https://api.vybit.net/v1/mcp and leave Authentication set to OAuth.
Check I understand and want to continue, then click Create as a plugin.
Sign in to Vybit when asked and approve access.
In a new chat, type @ and select Vybit.

On Business, Enterprise and Education workspaces, an admin may need to add the plugin or give you permission to add it.

ChatGPT asks you to confirm each action that changes something, such as creating a vybit or sending one. That is a good habit: read what it is about to do, then approve.

The full setup for each assistant also lives on our AI assistants page.

Step 2: copy this prompt

Paste this into a new chat, then change the parts in brackets.

Use my Vybit connector to set up a team alert.

1. Create a vybit called "[Front desk bell]" that is private, with the
   default message "[Someone needs help at the front desk]".
2. Search the Vybit sounds for "[bell]" and show me the three best
   matches with their play links. Use the one I pick.
3. Invite these teammates to subscribe by email:
   [alex@example.com, sam@example.com, jordan@example.com]
4. Give me the vybit's trigger URL (https://vybit.net/trigger/ followed
   by its trigger key) so I can paste it into [my help desk / store /
   monitoring tool] as an outgoing webhook.
5. Send one test vybit with the message "Test: if you heard this, the
   alert works" so I can check the sound on my phone.

Each teammate gets an email invitation, signs in to Vybit (a free account is all they need) and accepts. From then on, every time the vybit fires, all of you hear it, on every device where you have Vybit.

Want it to ring on a schedule instead of from a webhook? Say so: "Make a vybit called Stand-up with a gong sound, on a schedule that rings the team at 9:55 on weekdays, Denver time." Use the word schedule for anything that repeats; Vybit's reminders are meant for one-off dates, like "Oct 20 at 7 PM, put the recycling out."

Step 3 (optional): wire it to the tool that knows when it should ring

Most tools that can send an outgoing webhook can fire a vybit. Paste the trigger URL into that tool's webhook or notification settings. A POST with a JSON body like {"message": "Ticket 4821: printer on fire"} replaces the default message for that one alert, so your team knows what happened before they pick up the phone.

If your assistant also has Zapier, Make or n8n connected, you can ask it to build that part too: "Create a Zap that sends my Front desk bell vybit whenever a new ticket is tagged urgent." Vybit is an official app on Zapier, Make and IFTTT, and there is a Vybit community node for n8n, so you can pick your vybit from a list in any of them.

How counting works

One notification is one vybit reaching one person, on all of their devices, and that includes you. So an alert that rings you and 8 teammates uses 9 notifications. Subscribers are free and unlimited, and nobody needs a seat to listen.

For a front desk crew of 9 with about 10 alerts a day, that is 9 x 10 x 30 = 2,700 notifications a month. A support team of 24 with about 20 alerts a day uses about 14,400.

Which plan fits

Free covers a small team with a few alerts a day: 1,500 notifications a month and 10 vybits.
Pro fits the crew of 9 above: 3,000 notifications a month, 20 vybits and 3 manager seats.
Team fits the support team of 24: 15,000 notifications a month, 50 vybits and 20 manager seats.

Manager seats are only for people who help you run the account (your vybits, sounds and logs). Everyone who just needs to hear the alert subscribes for free. The pricing page has the full comparison, and if you need more than Business offers, write to plans@vybit.net.

Your assistant can also tell you where you stand at any time. Ask it "How many Vybit notifications have I used this month?" and it will read your meter.

Originally published on Signals, the Vybit blog.

Introducing Pro, Team and Business

Vybit — Mon, 05 Oct 2026 14:40:11 +0000

Today Vybit's paid plans get new names: Pro, Team and Business. The free plan stays exactly as it was. If you already pay for Vybit, nothing about your plan or your price changes. Everything else in this post is about why we did it and who each plan is for.

Why rename plans that were working?

Our old plans were called Bronze, Silver and Gold. Metals are a fine way to say "bigger," but they say nothing about who the plan is for, and over the past year that turned out to be the question people were actually asking. When we looked at how paying customers really use Vybit, three patterns kept showing up.

A support team routes urgent Zendesk tickets to a vybit that rings all eleven people on the team at once, so the emergency is heard by whoever is closest, not by whoever happens to be watching the queue. A sales floor does the same with new leads. An online seller wires the store's order webhook to a cash register sound and hears every sale from wherever they are, and a bigger order rings a grander bell. A property company pushes alarms from dozens of buildings to the phones of the clients who own them, without building an app of their own.

None of those people were shopping for a metal. They were shopping for "everyone on my team hears it," or "I hear every sale," or "my clients hear my alarms." So the plans now say that.

Subscribers are free. You pay for what you send.

This is the part we care most about. Anyone can subscribe to your vybits from their own free Vybit account, and there is no limit on how many people do. Nobody needs a seat to listen, and there is no price per person.

What a plan gives you is a monthly pool of notifications. One notification is one vybit reaching one person, on all of their devices, and that includes you. A vybit sent to you and 19 teammates uses 20. So the Team pool of 15,000 a month can be about 20 alerts a day to a team of 24, or one alert a day to a few hundred people, or anything in between. You spend it where it matters.

Many team alerting tools charge per person, which quietly punishes you for telling more people. We think the opposite should be true. The whole point of a shared alert is that everyone who needs to know, knows. Pricing should not make you choose who gets left out.

Seats are a separate and smaller thing. A manager seat lets someone sign in with their own account and help run yours: your vybits, sounds and logs. Most teams need far fewer managers than listeners, and listeners never need a seat.

The three plans

Pro, $6 a month or $60 a year. For a solo operator or a small crew who wants every sale, lead or alert heard. 3,000 notifications a month, which is about 10 alerts a day to a team of 9, you included. 20 vybits and 3 manager seats.

Team, $29 a month or $290 a year. For support, sales and ops teams where one alert has to reach everyone. 15,000 notifications a month, about 20 alerts a day to a team of 24. 50 vybits and 20 manager seats. This is the plan we expect most teams to land on, and it is the one we built this change around.

Business, $79 a month or $790 a year. For companies that run on alerts, or that alert their own clients. The biggest pool: 50,000 notifications a month, which is about 40 alerts a day to 40 people, or one alarm a day to 1,600 clients. 100 vybits, 100 manager seats and priority support.

Yearly billing on every plan is ten months' price for twelve. Each paid plan also has a daily safety limit, set far above normal use, so a runaway automation cannot spend your whole month in an afternoon. If you use your whole pool, notifications pause until your monthly reset, or until you move up a plan.

Need a bigger pool than Business, or more than 100 manager seats? Write to plans@vybit.net.

What is not changing

The free plan is the same as yesterday: 10 vybits, 1,500 notifications a month, and no limit at all on how many vybits you subscribe to and hear. Receiving is free for everyone, always. Most individual users never need more than that, and we intend to keep it that way.

If you are already on Bronze, Silver or Gold, you keep your plan and your price for as long as your subscription stays active. You do not need to do anything. If you ever choose to switch, the new plans are what you will switch to.

Every plan, free or paid, still comes with the things that make Vybit Vybit: record or choose a sound for every alert, trigger it from any webhook, schedule, geofence, reminder, automation platform or AI assistant, and share it with the people who should hear it.

Where to go from here

The pricing page has the full comparison. To choose a plan, sign in at my.vybit.net, open your profile and pick one. Over the coming weeks we will publish a short setup guide for each of the three patterns above, with ready-made recipes and a prompt you can hand to your AI assistant, so that "urgent ticket rings the whole team" is a five-minute job rather than an afternoon.

If a sound has ever told you something before a screen could, you already know why we build this. Now the plans are named for you.

Originally published on Signals, the Vybit blog.

A Grander Bell for a Bigger Sale

Vybit — Thu, 20 Aug 2026 00:11:37 +0000

Last time we imagined a shop minded by software, and one line in it keeps coming back to me: a bigger sale rings a grander bell. It is a nice image. It is also a recipe, and today we are going to cook it.

The original post embeds an interactive demo: click an order, watch it route through the workflow, and hear the vybit land, with a swap-sound control on every branch. Words cannot play audio, so go press the buttons.

▶ Play the demo on the Vybit blog, sound on

That demo is not a mockup of an idea. It mirrors a live workflow, and the sounds it plays are the vybits it fires. Nothing about the sounds is hard-coded either. Swap any branch's sound and the same workflow speaks with a different voice. When you build this yourself you pick every sound from a library of thousands, or record your own, which is the entire point: the sound means whatever you decide it means.

Here is the situation. Something happens in your business, an automation platform catches it, and a notification goes out. This is arguably the most common shape in all of automation. Zapier's own guide to team notifications recommends filtering alerts so high-value sales stand out. The n8n template library is stacked with order alert workflows, including one dedicated entirely to VIP alerts for big Shopify orders. And when IFTTT published its most used applets of 2025, the pattern across the board was small automations that tell you something the moment it happens.

So the ecosystem already agrees: route events by what they mean, then notify. The part everyone leaves on the table is the notification itself. Every branch of your carefully constructed workflow, the happy path, the sad path, the champagne path, arrives on your phone as the same generic ping. You built a workflow that knows the difference, but your ears don't.

Vybit fixes exactly that. Give each branch its own vybit, and each outcome its own sound. Then the routing your workflow does becomes routing for your ears.

One webhook, three outcomes, three sounds

An online shop where orders come in through a webhook. Three things can happen, and each deserves a different reaction from you:

A payment fails. That is a sad little wah wah horn. You know without looking that something needs attention, and you know it is not an emergency siren, just a note to check the dashboard when you have a minute.

A normal order lands. Cha-ching. The oldest good sound in commerce now back in service. You are cooking dinner and the register rings and you smile and keep stirring.

A big order lands, say $500 or more. That one struts in on a funk guitar riff. James Ritty's Incorruptible Cashier rang one bell for every sale because one bell was all the hardware could do. We can do better: a grander bell for a bigger sale.

How it is wired

We built the real thing in n8n, and the whole workflow is five nodes. A Webhook node receives the order as JSON:

{
  "order_id": "1043",
  "customer": "Summit Gear Co",
  "total": 1250,
  "payment_status": "paid"
}

A Switch node routes on two fields. If payment_status is failed, take the first branch. If it is paid and total is $500 or more, take the VIP branch. Otherwise it is a regular order. Each branch ends in the official Vybit node, which triggers one of three vybits: Payment Failed, VIP Order, or New Order. Each vybit carries its own sound and a message template that fills in the order details, so the notification tells you what happened even if you do want to look.

That is the entire build. Three vybits, one router, maybe ten minutes.

The same shape, on any platform

Nothing about this is specific to n8n. The pattern is trigger, branch, vybit, and every major automation platform speaks it natively. Vybit is a partner integration on all of them.

In Zapier, use Paths to branch on payment status and order value, and end each path with the Vybit action. In Make, a Router with filters on each route does the same job, feeding the Vybit app. In IFTTT, where applets are single-purpose by design, the branching just moves upstream: one applet per outcome, each ending in the Send Vyb action. And if your event source can send a webhook but you use no platform at all, each vybit has its own trigger URL you can call directly.

The three vybits never change. Your sounds are yours, wherever the workflow runs.

Every workflow has branches worth hearing

Orders are the friendly example, but listen to how many workflows have this exact shape. A lead comes in: hot lead, routine lead, spam. A nightly backup: finished clean or did not. A deploy: shipped or rolled back. n8n's template library has an entire genre of error alert workflows because the sad path is the one nobody can afford to miss. Wherever your workflow already makes a decision, that decision can have a sound.

The setup takes minutes. Create a vybit for each outcome at vybit.net, pick sounds that feel like what they mean, and point your workflow's branches at them. The free tier covers a shop's worth of ka-chings.

Your workflow already knows the difference between a good day and a bad one. Now your ears will too.

Originally published on Signals, the Vybit blog, where the demo actually makes noise.

The Information Is in the Sound

Vybit — Tue, 26 May 2026 13:52:10 +0000

Before there were screens, there was sound.

A bell in a tower could tell a whole town what time it was, that a fire had broken out, that someone had died, that it was safe to come back inside. Nobody had to look at the bell. The meaning traveled through the air and arrived to everyone at once. The information was in the sound.

Humans have always lived this way. We are built for it.

For most of our history, the things we most needed to know reached us through our ears. In ancient Israel, the shofar was sounded in set patterns where the rhythm of blasts was the message: gather, prepare, take heed. Across West Africa, drummers learned to reproduce the tones of speech so closely that a drum could carry a sentence across miles of forest, faster than a runner could. European villages hung a single bell that did many jobs at once. A slow, even toll marked a death. A frantic clanging, the tocsin, warned of fire or attack. A measured ring at dusk, the curfew, told everyone to bank the hearth fires for the night.

At sea, the ship's bell divided the day into watches so a sailor below deck always knew the hour. In cities across the early Islamic world, the call to prayer rose over the rooftops at fixed times, a single voice carrying a known meaning to everyone within earshot at once. None of this asked you to stop what you were doing and look at the source. You simply knew.

Then our information signals moved onto screens. And screens ask something of us that sound never did. They ask us to look.

Sight is an extraordinary sense, but it is a narrow and directed one. You have to aim it. Your sharpest vision covers only a few degrees at the center of your gaze, which is why we turn our heads, point our eyes, and lift a device up to our faces. To read a notification, you have to stop, orient, and decode text with the one sense that demands your full attention just to be used at all.

Hearing asks for none of that. It works in every direction at once. It reaches you with your eyes closed, your back turned, your attention somewhere else entirely. A parent asleep in a quiet house still wakes to the particular cry of their own child. We can recognize thousands of distinct sounds and pull meaning from each one in an instant, without looking at anything.

So here is the strange part. We carry devices that buzz at us dozens of times a day, and nearly every buzz sounds the same. The notification tells us only that something happened, not what. To learn the what, we do the thing billions of us do over and over: reach for the phone, look down, and read. We have taken the richest, most effortless information channel we own and flattened it into a handful of generic chimes.

Vybit puts the meaning back into the sound.

The idea is simple. You choose or record a distinct sound for each thing you care about, and from then on the sound itself tells you what happened. A rolling thunderclap when a storm moves into your area. A cash register for a sale. A particular voice saying the words you need to hear. One specific alarm, and only that one, for the cloud server you cannot afford to lose. When it plays, you already know, and your eyes never leave the road, the recipe, the conversation, or the work in front of you.

A sound does not have to be yours alone, either. Share one with your spouse so a soft chime means you are on your way home. Share one with your team so a single unmistakable alarm means latency just spiked on a critical cloud service. Share one with your customers so a signature sound announces that the thing they were waiting for has finally arrived.

That is where the name comes from. Each sound is a VIBE, and each VIBE is tied to one BIT of information. VIBE plus BIT: Vybit. The whole product is built on a fact about people that is far older than phones, which is that we read the world by ear remarkably well whenever sound is allowed to mean something.

The payoff is a kind of efficiency that sight cannot match, for the simple reason that sight has to be aimed and sound does not. A glance costs you your attention. A sound costs you nothing. You can be kept current all day long, told exactly what is happening around you and across your digital life, and never once break your focus to find out. The information is in the sound.

This matters more now than it ever has. We are moving into a world where software does more and more on our behalf, where assistants and agents carry out long tasks while we step away from the screen. The question stops being how to watch everything happen and becomes how to stay in the loop without standing guard over a progress bar. That is a question your ears were built to answer, and it is exactly where we are headed in the next post.

For now, the takeaway is primal. You do not have to look to know. You only have to listen.

Vybit is free to start, and it sends notifications with sounds you choose. If this idea resonates, subscribe to Signals on the Vybit blog and you will hear the next post the moment it lands.