Muse meeting connector for Google Meet, Microsoft Teams and Zoom

What is the Muse meeting connector?

The Muse meeting connector is a custom connector that lets Meta Muse put a recording bot in a Google Meet, Microsoft Teams or Zoom call through the MeetStream API. You paste one prompt into Muse, Muse builds the connector, and from then on it can start a bot, check where that bot is, and fetch the transcript with speaker names.

The same thing gets called the Meta Muse connector, a Muse custom connector for meetings, a Muse meeting bot or a Muse notetaker. Meta does not ship one, so this is a connector you create yourself, in about two minutes, with the prompt and the OpenAPI file on this page.

Set it up in three steps

1. Get a MeetStream API key. Sign in to the dashboard, open the API tab and generate a key. Use a separate key for Muse so you can revoke it without touching anything else. New accounts start with $5 free credit, no card required.
2. Paste the connector prompt into Muse. Keep the key out of the prompt text. Share it as the connector credential instead, so it goes into secure storage rather than your chat history. The prompt names the connector MeetStream Meeting Bot.
3. Send a bot. In a new chat, give Muse a meeting link and a bot name. It calls create_bot, and you get a bot_id and a transcript_id back.

MEETSTREAM DASHBOARD

Create a new Custom Connector for an API called MeetStream. Here is the specification:

The API base URL is https://api.meetstream.ai/api/v1/
Authentication uses a token in the header. The header should be:
"Authorization": "Token <MeetStream API key, stored as a connector credential>"

The connector needs three operations:

1. Operation "create_bot"
   - Description: Sends a bot to a meeting link.
   - Method: POST
   - Path: /bots/create_bot
   - Body (JSON): {"meeting_link": "string", "bot_name": "string", "recording_config": {"transcript": {"provider": {"meetstream": {}}}}}
   - Response (201, JSON): {"bot_id": "string", "transcript_id": "string", "meeting_url": "string", "status": "string"}

2. Operation "get_bot_status"
   - Description: Gets the current status of a bot.
   - Method: GET
   - Path: /bots/{bot_id}/status
   - Path Parameters: {"bot_id": "string"}
   - Response (JSON): {"bot_id": "string", "status": "string", "custom_attributes": {}}

3. Operation "get_transcript"
   - Description: Fetches the final transcript for a completed meeting.
   - Method: GET
   - Path: /transcript/{transcript_id}/get_transcript
   - Path Parameters: {"transcript_id": "string"}
   - Response (JSON): a list of segments, each {"speaker": "string", "transcript": "string", "start_time": number, "end_time": number, "words": [...]}

Please build this connector and name it "MeetStream Meeting Bot".

Using the MeetStream Meeting Bot connector, send a bot named "My AI Assistant" to this meeting: https://meet.google.com/abc-def-ghi

Wait for the meeting to finish, then fetch and display the full transcript.

Meta says Muse keeps working on longer tasks after you close the app. You can also ask for the status at any time, and for the transcript once the bot has left. The connector spec is also available as a file: openapi.json, the same three operations in OpenAPI form, for Muse or any other agent that prefers a schema over prose.

What is the status of the bot with ID 123e4567-e89b-12d3-a456-426614174000?

What each status means

The status endpoint returns one word. These are the ones Muse will see most, in the order they happen. The debugging guide has the full list.

Zoom, Google Meet and Microsoft Teams

Muse sends the same request for all three. What differs is how each platform lets a bot in.

Muse connector for Google Meet

Give Muse a meet.google.com link and it sends the bot straight there. By default the bot joins as a guest, so a participant sees a request to join and clicks Admit. With host management on, only hosts and co-hosts see that request. A signed-in bot on your workspace domain skips the lobby.

Muse connector for Microsoft Teams

Teams meetings work from the link alone, with no Azure app registration and nothing for your IT team to approve. Most tenants hold external participants in the lobby, so an organiser admits the bot. Everything after that, the recording and the transcript, is identical to the other two platforms.

Muse connector for Zoom

Zoom adds one step: the host grants recording permission after the bot joins, and the bot leaves cleanly if that is declined. Meetings hosted by other people need a production-approved Marketplace app, which the Zoom integration page walks through.

Speaker-labelled transcripts come from the in-house meetstream provider set in the prompt. Deepgram, AssemblyAI, JigsawStack and Sarvam are available through the same recording_config.transcript.provider field; see the transcription API.

Permissions and security

Four parties have a say when an agent joins a meeting on your behalf. Each one is worth a sentence.

• Meta. Muse builds custom connectors on your instruction, and Meta does not review them. Credentials you share go into secure storage Muse cannot read. Nothing Muse does reaches the internet unless a separate Sentinel agent approves it. You can change or disconnect a connector under Settings, then Connectors.
• MeetStream. The API key is your account. Give Muse its own key, revoke it from the dashboard when you stop using the connector, and never paste it into a chat or a repository. Recording storage includes 30 days, and security and compliance covers the rest.
• The meeting platform. The bot is a participant. The host admits it, and on Zoom the host also grants recording. The host can remove it at any time, like any other attendee.
• The people in the room. Tell participants that an assistant is present and recording. Recording consent rules differ by country and by company policy, and the bot name is the simplest place to say what it is.

Frequently asked questions