2
Meeting Bot
Source: twentyhq/twenty#7008 · opened by @FelixMalfait
1. Define env vars and pass them as client config MEETING_BOT_PROVIDER=aimeetingbot MEETING_BOT_API_KEY=xxxx Pass the meeting bot provider to the frontend in clientConfig. Note this is a standard across our codebase, we use a “driver based” approach for all external providers, even if there’s just 1 provider implemented. 2. Add an option to opt-in in integration page Frontend: design will be confirmed by @Bonapara Backend: we need to add a new billingSubscriptionItem to the subscription, which will track that the user has opted-in to the meeting bot extension. I think we need a custom resolver for that. Related: #5247 3. Add an option to opt-in to MeetingBots in calendar settings Frontend: design will be confirmed by @Bonapara. Conditionally display section "meeting bot" with a setting to define when meeting bots should be automatically added to meetings Backend: we need to introduce a new column on calendarChannel table, which we can call meetingBotAut…
No pledges yet. Be the first to back this.
Comments
Similar requests
Would an Inbox Zero × Twenty integration be useful?
2 votes · 0 comments
Feature: allow setting a Dashboard as the default landing page (post-login home)
3 votes · 0 comments
Missing Sorting Functionality for Related Records in Object Relations
6 votes · 0 comments
Add date range filters to Calendar tab on record pages
2 votes · 0 comments
Guide to success for this project. Invoicing, Stable/pre-release, automation, Messaging.
4 votes · 0 comments
No comments yet.