@anastazja.rajmar In your API key field do you have “Bearer” in front? You’ll need that in order to create rooms with the plugin.
It should look like the screenshot below.
Hmm I just tried it on this demo and it’s still able to create a room.
I’ve also seen this once when someone has reached their room limit on their domain.
Could you pm a link to your editor and/or pm your Daily domain and I can explore further?
Also making sure there aren’t any extra spaces at the end of the API key.
But if you dm a link to your editor and or share you Daily domain I can look more into the logs.
Lola
I found the mistake!
I have full of rooms 50/50. I just deleted them and it`s works. 
How I can automatically deleted rroom, if for example I leave meeting or just close this page?
Thank you!
@anastazja.rajmar Glad you found it! You can use the exp property if you have an idea in advance when your room will end or a general timeline. When the room is expired it will automatically be deleted and no one will be able to join the room in the future.
To do that you’ll convert the date/time to a unix timestamp and then convert it to seconds (divide by 1000). Here’s a sample editor with with a room that expires 10 minutes after it’s created (but you could do this with any date or time period) and a screenshot of what that looks like
Oh. That`s cool!
You helped me!!!
Thank you very much 
Hi @lola
Excited to use your tool. I’ve got a couple questions to get started:
- Are the rooms permanent (user owns their own room) or temporary for each session (50 new rooms each month)?
- Since a meeting token requires the name of a specific room to join, where do we set the room name in the plugin?
Thanks so much for the help.
Cheers
Hello @jasonturo!
Answer to question 1
Rooms exist until they are deleted or expire. You can delete a room with the “Daily - delete room “action or make the room expire by setting an exp time when you create a room.
Here’s an example of creating a room that expires 10 minutes after it expires.
If the room is not deleted or expired you can join and leave the room as often and for as long as you’d like.
Answer to question 2
You can access the name of the room in a workflow when creating the room.
Here’s an example of creating a room and then creating a meeting token for that room but you could also set this workflow up so that the room name gets saved in your database so you can use it later!
The room name is also the string after the / in your room URL. So if your room URL was something like https://apps.daily.co/N0M82Frn6WLvSTPqF197 N0M82Frn6WLvSTPqF197 would be the room name.
Hope that helps!
Awesome. Thank you, @lola
Also, in the case of a paid private meeting, how would you recommend providing the paying client access to the meeting with a token in their calendar invite? It seems that we wouldn’t want to send the link to the host’s meeting room, since we only want the client accessing that on their scheduled times, and not other times or sending the link to others.
Thanks for the insights.
Cheers
@jasonturo Hello!
I think there are a couple of options!
You could send a link directly or embed the link within your application. If hosts will be reusing parameters, you might only want to give tokens to owners and set the rooms enable knocking parameter to yes.
The owner/host will have to let users into the chat rooms when enable knocking is set to yes. Having an owner token will also give the host the ability to mute users, remove them from rooms etc.
This is what it looks like to create a private room in which knocking is enabled.
And this is what it looks like to create an owner meeting token.
Also another caveat since sometimes folks have missed this. You’ll want to make sure you put the appropriate meeting token in the meeting token field when joining a room. That’s also accessible in the workflow once you create it.
All of this is in the demo editor.
Lola
Hi!
I have a little problem with plugin. When I start the meeting and join a conf i start to listen for an event. On desktop browser when I left the meeting it work perfectly. But when I run same action, on same page with same user but page is running inside the BDK Wrapper it’s not working at all. Do you know what cause the problem?
@kamil.tarczynski I don’t think I’ve seen that before, I know a few users who have wrapped their Bubble apps with Daily. What actions are you having the user take when they leave the meeting? And what device are you using?
I’ll try to recreate this to see what I can find!
We simply start meeting:
When user is in the meeting we click on the leave button and after that one of those should fire:
But on the wrapped app (we using BDK) it simply does not work - on desktop browsers it works perfectly.
Hey @kamil.tarczynski! I just tried a demo in the BDK wrapper that shows an alert once the user leaves a meeting and it worked in the wrapper.
What are the actions that you’re trying to take when a user leaves the meeting? Looks like it’s cut off in that second screenshot. I think a few actions, like opening a URL don’t work the same in a wrapped app.
Also caveat with BDK, especially if users will be using on Android, you’ll need to make sure that WebRtc is enabled for android. Androids require additional permission to support accessing audio and video from a browser. Gonative supports this setting for wrapped apps, but I don’t have a definitive answer for BDK
We simply change thing in the DB and showing some elements on page. And that’s strange because in the chrome it works but in the bdk not. 
@kamil.tarczynski That’s so odd! If you DM me a link to your editor, happy to take a look further to see if I can figure anything out!
Lola
Hi Lola,
I am not able to find the data source for the meeting information data group. You can see the screenshot of my editor. Can you please help ?
Hello @rachanabagde1996 ! What data are you trying to display and show? If you let me know a little bit more about what you’re building there might be an even more streamlined approach!
You’ll typically need to use the get data from external API to access that plugin info. Bubble treats plugins as such in the data source. Here’s what that looks like:
And here are two demos of using information from the plugin as data