docs: add Attendee meeting bot integration#124
Conversation
|
Warning Review limit reached
More reviews will be available in 8 minutes and 44 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a new ChangesAttendee Integration Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@chapters/integrations/attendee.mdx`:
- Line 43: The sign-up link on the attendee integration page has an incorrect
endpoint. Locate the link with the text "Sign up for a Gladia account if you
don't have one" and update its href from `https://app.gladia.io/auth/signin` to
`https://app.gladia.io/auth/signup`. The signin endpoint is for existing users
logging in, while signup is the correct endpoint for new account creation that
matches the instruction text.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 59784ea2-048c-4807-bbde-afac400123bc
📒 Files selected for processing (3)
chapters/integrations/attendee.mdxdocs.jsonsnippets/integrations-cards.mdx
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
What
Adds a Gladia integration page for Attendee (attendee-labs/attendee), the open-source universal Meeting Bot API. Modeled on the existing Recall and Meeting BaaS pages.
Changes
chapters/integrations/attendee.mdxdocs.jsonsnippets/integrations-cards.mdxContent (sourced from attendee-labs/attendee, not guessed)
POST https://app.attendee.dev/api/v1/botswithAuthorization: Token <key>transcription_settings: { "gladia": {} }enable_code_switching,code_switching_languagestranscript.updatewebhook or/transcriptendpointSummary by CodeRabbit