Hi everyone, first post from the Vybit team.
My Switch node already knew the difference between a failed payment, a regular order, and a $500+ order. My phone played the same ping for all three, so I still had to pick it up and look.
So we built a node for that. Vybit (@vybit/n8n-nodes-vybit, verified) triggers push notifications to Android, iOS, and web, and each notification carries its own sound. You pick the sound from a big library or record your own. Beyond sending notifications, the node covers the full API (34 operations: vybits, subscriptions, reminders, sounds, logs) with API key or OAuth2 auth. On n8n Cloud, sign-in is one click: add the node, choose Connect my account, and approve in Vybit. No OAuth app to register.
Example: order alerts you can hear
Five working nodes:
- Webhook receives
{ order_id, customer, total, payment_status } - Switch routes on
payment_statusandtotal - Vybit: Payment Failed plays a sad horn
- Vybit: VIP Order ($500+) plays a funk riff
- Vybit: New Order plays a cha-ching
Now I know which branch fired without looking. The same shape works for anything that already branches: backup ok vs failed, hot lead vs routine lead, deploy shipped vs rolled back.
Here’s the workflow. Paste it into your canvas, create one vybit per outcome in the Vybit app, drop each key into its node, and connect your Vybit credential:
The full write-up has a playable demo where you can fire the webhook and hear each branch in your browser:
Install it from the nodes panel (search “Vybit”), or on self-hosted via Settings > Community Nodes. npm: https://www.npmjs.com/package/@vybit/n8n-nodes-vybit
Happy to answer questions or take feature requests for the node. What workflow would you give its own sound first?
Maren, Vybit