Adding an Audio alert at specific times during a video call

Nah, it’s good to think of these edge cases, the sooner the better.

But I’m guessing you’d need to trigger the countdown at the same time as the user is added to the conference.
Or include the start of the countdown as he opens the daily.co video.
It’s a bit hard for me to visualize this without knowing more.

That’s why you need a server-initiated procedure to cover all cases. If some other user adds him that’s the only way to notify his client-side.

How can you add someone to a video call with daily.co and not have the ability to start the timer?

I’ve built, extensively tested and launched the exact thing OP is asking for with the daily plugin, what you’re describing has never been an issue.

Not to the videocall, but to the event that holds the videocall, similar to Google Calendar events, where people is invited. I might have misunderstood what OP exactly wants, tho.

As I understood, the OP wants a feature that reproduces a sound when the event starts, similar to a Google Calendar notification, whether or not you are in the videocall. For that you’ll need a server-initiated procedure, due to the above mentioned reasons.

If the sounds are to be reproduced only if the user is already in the videocall, the situation changes, and the client-side timer based solution is valid, because can start the timer as part of the videocall join logic.

If I follow you here.
You’re thinking of a real-time sound when something changes in the database.
Like a notification showing up if someone sends you a message in a chat? (no refresh needed)
But instead of a notification, a sound notification is heard?
I would still build it like an in-chat(sound) notification.
No “schedule an API” needed. In fact, I think bubble used to have, and I might still have a real-time bug when scheduling a backend workflow and having it show up on the other user in the front-end with no refresh.

That’s it, something changes in DB and that serves for signalling users client-side.

I agree. I’ve suffered it myself. That’s why exploring websockets for this kind of need is what I am currently exploring.

I’ve built this too solo, and the app has been tested a 1000 times and is in production. It works perfectly if the user saves his message to the DB, the message shows up for the other user with the notification all of the time.

I haven’t tested saving the message as a backend workflow, people seem to struggle specifically with that. I might test it someday and report back.

Hi, would you happen to have a solution?

If I follow you here.
You’re thinking of a real-time sound when something changes in the database.
Like a notification showing up if someone sends you a message in a chat? (no refresh needed)
But instead of a notification, a sound notification is heard?
I would still build it like an in-chat(sound) notification.
No “schedule an API” needed. In fact, I think bubble used to have, and I might still have a real-time bug when scheduling a backend workflow and having it show up on the other user in the front-end with no refresh.

So is this my best option? Okay I will give it a try.

Well Daily.co does not seem to offer the chance to reproduce sounds via API, so you’ll have to reproduce it client-side via Bubble actions.

Then, I would approach this by signaling appropriate clients to reproduce a sound at a given time. You need a backend mechanism to signal at a given time and a frontend mechanism to receive that signal and reproduce the sound locally.

The conference creator can schedule an API workflow 15 mins before the conference starts, to open it for attendees. Said API workflow can schedule another API workflow 15 mins later, to signal attendees the conference starts, and another API workflow whenever the conference is to end that does the same thing. You can schedule as many as you need for differen times.

Signalling is done through a User’s field of type yes/no that the backend sets to true.

For receiving the signal in the client, you’ll have to set up a Do When condition is true event that reacts to said User’s field set to yes. You set it back to no and reproduce a sound via Javascript.

The solution is more complicated than just posting it here.
If, you really need real-time notifications. Which isn’t what you asked for in your OP. Then I would go to youtube and search for: “bubble.io chat notification” to try and understand the build and how you can modify it to your needs or use GPT.

But if you just need to play a sound at certain times the answer is really simple:
Event: on page load: action: Start countdown X
Event: When countdown X has ended: play sound

Thanks, I will look into that for sure.

But if you just need to play a sound at certain times the answer is really simple:
Event: on page load: action: Start countdown X
Event: When countdown X has ended: play sound

I’ve tried doing this and it’s still not playing any a sound in the start time or end time of the meeting.




I’m using the plugin “timer” by Copilot

And, you’re doing it in a custom event, that will likely not work.
Get the plugin I’m using and use the same event as the screenshot I attached, that’s the most straightforward way to get it to work. Unless you have some good reason to use the plugin you’re using, but a ‘custom event’ needs to be triggered, I guess it could be triggered by countdown ending. But that’s something else. It’s early here, but what you’re doing will not work currently but you got this. Just get the correct plugin, add the correct event according to my screenshot. Make sure to load the countdown with the right time and it will work.

Okay, I have downloaded the plugin. Where is the event "Countdown to start has “started”? I see ended, but where is started?

Your solution works, but I only see a “countdown ended” event. Where is the “countdown started” event?

I think I know how to do it now, I will left you know what i came up with.

Great question.
I picked the event: ‘on page load’.
Action: start countdown.

But whatever event you want to use. Have fun with it, you’ll figure it out.

This topic was automatically closed after 70 days. New replies are no longer allowed.