One of Attendee’s biggest strengths is providing a single, unified API for bots on Zoom, Google Meet, and Microsoft Teams. While our API normalizes the experience, each platform has unique authentication methods. Understanding these nuances is the first step to a successful integration.

Platform Capabilities at a Glance

Before diving in, here’s how Attendee handles integration across the major platforms. This will help you understand what to expect.

Zoom Integration

Zoom provides the most mature environment for bots, offering deep control via its Meeting SDK and REST API. Attendee leverages this for a stable and feature-rich experience.

Key Requirements

To integrate with Zoom, you must create your own **OAuth App** in the Zoom App Marketplace. This gives your bot a unique identity and the necessary permissions to join meetings on your behalf.

Example Credentials Structure

{
  "client_id": "your_zoom_client_id",
  "client_secret": "your_zoom_client_secret",
  "account_id": "your_zoom_account_id"
}

This structure illustrates the credentials you will add in the Settings → Credentials section of your Attendee dashboard. Attendee securely stores and uses these keys to authenticate on your behalf when a bot is launched.

Google Meet Integration

Google Meet does not offer an official API for bots. To solve this, Attendee uses a sophisticated **headless browser automation** technique. Our bot joins meetings just like a human user, but runs virtually on a server.

Key Requirements

Authentication is handled via a standard Google Cloud Project with OAuth 2.0 credentials. You'll need to authorize Attendee to act on behalf of a Google account, which will be the "user" that joins your meetings.

Example Credentials Structure

{
  "client_id": "your_gcp_client_id.apps.googleusercontent.com",
  "client_secret": "your_gcp_client_secret",
  "refresh_token": "user_refresh_token_with_calendar_scope"
}

This structure illustrates the credentials you will add in the Settings → Credentials section of your Attendee dashboard. Attendee securely stores and uses these keys to authenticate on your behalf when a bot is launched.

Microsoft Teams Integration

Microsoft provides deep integration into the Teams ecosystem via the Bot Framework and Microsoft Graph API. This allows for powerful bots that can reliably access meeting data.

Key Requirements

Setup requires an Azure account to register your bot with the Bot Framework. Authentication uses Azure Active Directory (AAD) and requires careful configuration of API permissions in the Azure portal.

Example Credentials Structure

{
  "tenant_id": "your_azure_tenant_id",
  "client_id": "your_bot_client_id",
  "client_secret": "your_bot_client_secret"
}

This structure illustrates the credentials you will add in the Settings → Credentials section of your Attendee dashboard. Attendee securely stores and uses these keys to authenticate on your behalf when a bot is launched.

Universal Best Practices

Regardless of the platform, follow these rules for a smooth integration:

• Use the Dashboard for Secrets: Always enter your credentials directly into the Attendee dashboard. This is the most secure method.
• Grant Correct Permissions: When creating your apps (in Zoom, Google Cloud, or Azure), ensure you grant the minimum required permissions for bot operation, such as joining meetings and accessing media streams.
• Test Each Platform: After adding credentials for a platform, launch a test bot to ensure the authentication is working correctly before moving your integration to production.