A Whereby MCP for rooms your workflows create, record, and clean up
Connect one Whereby Embedded API key and meetings, cloud recordings, transcriptions, call quality insights, and room branding become workflow steps. An automation can mint a room URL the moment a booking is confirmed, queue a transcription as soon as the recording lands, and hand an agent the metadata it needs without anyone opening the Whereby dashboard.
What the Whereby MCP connector does
The Whereby connector for Mattering Automations is 22 nodes on the Whereby REST API v1: meetings from creation through lookup and deletion, cloud recordings with metadata, expiring download links and both single and bulk deletes, transcriptions queued against an existing recording with the same access link and delete pattern, room and room session insights with participant listings and per participant call quality detail, and the three room theme writes that set a room's colors, in call background, and knock page background. One Whereby Embedded API key, sent as an HTTP Bearer token, authenticates all of it.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can look up which recordings exist, check whether a transcription has reached the ready state, mint a download link at the moment it is needed, and write the result somewhere a person will actually see it, all through the same nodes an automation uses.
The platform angle is what makes this more than an API wrapper. A Whereby room rarely stands alone: something schedules it, someone joins it, and something has to happen with what it produced. On the Mattering canvas the room creation sits next to the booking record, the recording sweep can open a task in Mattering Productivity, the transcription link can be attached to a deal in Mattering Sales, and the credential lives once with the rest of your connector secrets rather than in a script. It is a visual workflow builder, so the steps and their conditions are configured, then reused by both automations and agents.
The safety modeling is stated plainly. Of the 22 nodes, 12 read and 10 act, and five are flagged destructive: the meeting delete, the recording and transcription deletes, and the two bulk deletes. Two behaviors deserve reading before you wire anything up. Deleting a meeting tears down the room itself, so anyone currently in the call is removed and that room URL never works again. And both bulk deletes answer immediately with a success status before anything has actually been removed, because Whereby runs them as a background job with no id to poll or cancel, so a green step means the job was accepted rather than finished.
One connection, three surfaces
- Visual automations. Drag Whereby nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Whereby node, ready to drop on the canvas
22 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 12
Whereby: Get Meeting
Fetch one meeting by id, including its room URL and its start and end dates.
Whereby: Get Participant Session Details
Call quality detail for one participant in one session: display name, role, user agent, and sampled network series for packet loss and bitrate in both directions, taken at the reported sampleRateMs interval. Returns a bare JSON ARRAY, so paths start data[0], not data.results[].
Whereby: Get Recording
Fetch one recording's metadata by id: filename, size, room session id, and start and end dates.
Whereby: Get Recording Access Link
Mint a temporary download URL for a recording, plus the millisecond timestamp at which it expires. The link EXPIRES (one hour by default, 12 hours at most), so fetch it when you are about to download and never store it as a permanent address. Available for Whereby hosted recordings only: a recording written to your own S3 bucket is fetched from that bucket instead. Nothing is deleted or changed by this call.
Whereby: Get Room Insights
Usage summary per room: participant, recorder and streamer minutes, unique participant counts, session count, and the average rating. Also the only place this API enumerates room names. Read the totals as LIFETIME figures for each room, not as activity inside the requested date range: the createdAt filter selects which ROOMS are returned by when they were created, and a room's totals keep growing for as long as it exists. rating is an average and must never be summed.
Whereby: Get Room Session Insights
Usage per SESSION of one named room: when the session started and ended, participant, recorder and streamer minutes, unique participant counts, and rating. This is the node that turns a room name into the session ids the participant nodes need.
Whereby: Get Transcription
Fetch one transcription's metadata by id, including its state, which is what tells you whether the file is ready to download.
Whereby: Get Transcription Access Link
Mint a temporary download URL for a transcription file, plus the millisecond timestamp at which it expires. The link EXPIRES (one hour by default, 12 hours at most), so fetch it when you are about to download rather than storing it. Available for Whereby hosted transcriptions only (storageType WHEREBY_HOSTED); a SELF_HOSTED transcription is fetched from your own bucket. Nothing is changed by this call.
Whereby: List Meetings
List the organization's meetings, newest page first, with an opaque cursor for the next page. Also the connector's auth probe: it needs no parameters and a bad key returns 401.
Whereby: List Recordings
List cloud recordings with their filename, size, room session id, and start and end dates. This is metadata only: use Whereby: Get Recording Access Link to get a downloadable URL.
Whereby: List Session Participants
List the participants of a room session with their display name, role, join and leave times, your own externalId if one was passed on the room URL, and any rating, tags and comment they left. Supply the room session id, or the externalId to trace one of your users across sessions.
Whereby: List Transcriptions
List transcriptions with their room name, state (ready, in_progress or failed), type (LIVE_TRANSCRIPTION from a session, or RECORDING_TRANSCRIPTION generated from a recording), duration and storage type. Metadata only: use Whereby: Get Transcription Access Link for the file.
Action nodes 10
Whereby: Bulk Delete Recordings
Destructive and irreversible: delete many recordings at once. Whereby schedules a background job and returns 204 IMMEDIATELY, before anything has been deleted, so a success here means the job was accepted rather than finished; poll Whereby: List Recordings to see the effect. There is no undo and no job id to cancel. The call is idempotent.
Whereby: Bulk Delete Transcriptions
Destructive and irreversible: delete many transcriptions at once. Whereby schedules a background job and returns 204 IMMEDIATELY, before anything has been deleted, so a success here means the job was accepted rather than finished; poll Whereby: List Transcriptions to see the effect. There is no undo and no job id to cancel. The call is idempotent.
Whereby: Create Meeting
Create a meeting, which mints a transient Whereby room and returns its URL. The room exists from this call until one hour after endDate, then Whereby deletes it automatically. The API takes no attendee list and Whereby documents no invitation or notification for this call, so nothing is sent to anyone: distributing data.roomUrl is the caller's job. Reversible by Whereby: Delete Meeting, which removes the room.
Whereby: Create Transcription
Queue a transcription of an existing recording. Whereby schedules the job and returns 201 immediately, so the transcription is not ready yet: poll Whereby: List Transcriptions until the row's state is ready (it passes through in_progress, and can end at failed). Reversible by Whereby: Delete Transcription. Nothing is sent to any participant.
Whereby: Delete Meeting
Destructive and irreversible: delete a meeting, which tears down its room. Anyone in the room is removed and the room URL stops working; there is no undo and no way to recreate the same URL. The call is idempotent, so deleting an already deleted meeting returns the same 204. Returns no body.
Whereby: Delete Recording
Destructive and irreversible: delete one recording and its file. There is no undo and no trash to restore from. The call is idempotent, so deleting an already deleted recording returns the same 204. Returns no body.
Whereby: Delete Transcription
Destructive and irreversible: delete one transcription and its file. A transcription made from a recording can be regenerated with Whereby: Create Transcription while that recording still exists; a session transcription cannot be regenerated at all. The call is idempotent. Returns no body.
Whereby: Set Room Background
Set one room's in-call background from Whereby's own presets (a color palette and an optional image), overriding the organization branding for that room only. Reversible: send palette default and theme default to restore the plain default. Uploading a CUSTOM background image is not available here: that variant of the endpoint takes a binary multipart file, which a canvas node cannot author. Returns no body.
Whereby: Set Room Colors
Set one room's primary, secondary and focus colors, overriding the organization branding for that room only. Reversible: send tokensPreset default to hand the room back to the organization defaults. Returns no body.
Whereby: Set Room Knock Page Background
Set the background of one room's knock page, the waiting screen a visitor sees before being let into a locked room, from Whereby's own presets. Reversible: send palette default and theme default to restore the plain default. Uploading a CUSTOM image is not available here: that variant takes a binary multipart file, which a canvas node cannot author. Returns no body.
Connecting Whereby takes one credential
Whereby authenticates every API v1 request with an HTTP Bearer token: an Authorization header carrying the word Bearer and your API key. The key is minted in the Whereby Embedded dashboard, and it is the only credential the API documents; there is no OAuth flow, no signed request, and no key query parameter. Whereby's own security note is blunt about the consequence: the token is handed to the client and it is the client's job to keep it secret, so treat it as a full access credential for the organization's rooms, recordings, and transcriptions.
In the Whereby Embedded dashboard, create an API key and copy it. It is one string with no client secret alongside it.
In Mattering Automations, open Connectors, click Add Connector, choose Whereby, and create a credential with the API key as the bearer token.
Click Test Connection. Mattering calls Whereby's meetings list endpoint, which needs no parameters: a results list, even an empty one, proves the credential, and a 401 saying the access token is missing or invalid means the key is wrong or was revoked.
All 22 Whereby nodes appear in the canvas palette. Run Whereby: List Meetings or Whereby: List Recordings first, because the ids they return are what the get, link, and delete nodes ask for.
Common uses for the Whereby MCP
Mint a room the moment something is booked
Whereby: Create Meeting turns a confirmed booking into a live room URL inside the same run that created the booking record. Two properties make it safe to automate: the API takes no attendee list and Whereby documents no invitation or notification for the call, so nothing is sent to anyone and distributing data.roomUrl stays your workflow's decision, and the room deactivates by itself one hour after the endDate you set and is deleted automatically within 24 hours of that endDate. Send the URL by whatever channel you already use, or park it on a record and let the reminder step carry it.
A recording archive that never stores a dead link
Whereby: List Recordings sweeps the metadata (filename, size, room session id, start and end dates) into a Mattering database on a schedule, and Whereby: Get Recording Access Link mints the download URL only at the moment something is about to fetch the file. That split matters because the access link expires: one hour by default and 12 hours at most. Store the recording id, never the link. The link nodes are also for Whereby hosted files; a recording written to your own S3 bucket is fetched from that bucket instead.
Transcriptions queued and collected without a person waiting
Whereby: Create Transcription queues a job against an existing recording and returns before the work is done, so the honest pattern is a poll rather than a straight line. A scheduled workflow runs Whereby: List Transcriptions, looks for rows whose state has turned ready (they pass through in progress and can end at failed), calls Whereby: Get Transcription Access Link for those, and files the text where the team reads it. Whereby: Get Transcription answers the same question for one known id.
Call quality triage an agent can actually run
When someone reports a bad call, the trail is three nodes deep. Whereby: Get Room Session Insights turns a room name into its sessions with their minutes and ratings, Whereby: List Session Participants shows who was in a given session with their join and leave times and any rating, tags, or comment they left, and Whereby: Get Participant Session Details returns the sampled network series for one participant, packet loss and bitrate in both directions. The rating, tags, and comment require session ratings to be enabled for the organization, so they stay empty until someone turns that on. All three are reads, which makes them a comfortable surface to hand an AI assistant on a support queue.
Per room branding set by the workflow that created the room
Whereby: Set Room Colors writes a room's primary, secondary, and focus colors, and Whereby: Set Room Background and Whereby: Set Room Knock Page Background choose from Whereby's own palette and image presets for the in call view and the waiting screen. Each override applies to that one room and each has a documented way back, so a client facing room can carry that client's colors for its lifetime and hand the room back to the organization defaults afterwards. Uploading a custom image is not available through these nodes: that variant of the endpoint takes a binary file upload.
Retention cleanup with the asynchrony made visible
A scheduled sweep can read what is older than your retention window and remove it with Whereby: Delete Recording, Whereby: Delete Transcription, or the filtered Whereby: Bulk Delete Recordings and Whereby: Bulk Delete Transcriptions. Build the verification in rather than trusting the status: both bulk nodes return success as soon as Whereby accepts the background job, before any file is gone, so the workflow should re-run the matching lister afterwards to confirm the rows disappeared. All four are flagged destructive, there is no trash to restore from, and a transcription made from a recording can only be regenerated while that recording still exists.
Example: From booking to transcript, with nothing sitting in an inbox
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a booking is confirmed in your scheduling system and fires an inbound webhook carrying the attendee and the end time.
Whereby: Create Meeting mints the room, with endDate set from the booking, and returns the room URL for the workflow to distribute.
The workflow writes the room URL and the meeting id onto the booking record and sends the invitation through the channel you already use, because the Whereby call itself notifies nobody.
On a schedule after the call, Whereby: List Recordings finds the new recording by its room session and start date.
Whereby: Create Transcription queues the transcript against that recording id, and a later run of Whereby: List Transcriptions waits for the row to reach the ready state.
Whereby: Get Transcription Access Link mints a fresh download URL at the moment it is needed, and the workflow opens a task in Mattering Productivity with the transcript attached for whoever owns the follow up.
Whereby MCP questions, answered
What Whereby operations are supported?
22 nodes on the Whereby REST API v1: 12 query nodes and 10 action nodes. Meetings (list, get, create, delete), recordings (list, get, access link, delete, bulk delete), transcriptions (create, list, get, access link, delete, bulk delete), insights (rooms, room sessions, session participants, and per participant call quality detail), and the three room theme writes for colors, in call background, and knock page background. Deliberately not included: the session summaries family, the room logo upload, and custom background image uploads, each for a stated reason rather than an oversight.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Does creating a meeting send an invitation to anyone?
No. The create call takes no attendee list and Whereby documents no invitation, email, or notification for it. It mints a transient room and hands back its URL, which means distributing that URL is entirely your workflow's job, and it also means the node is safe to run speculatively: nothing reaches a human until you send it. The room stays reachable until one hour after the endDate you set, when Whereby deactivates it, and Whereby deletes it automatically within 24 hours of that endDate. Whereby: Delete Meeting removes it sooner.
What are Whereby's API rate limits?
Whereby meters the API in points rather than plain request counts, and what a call costs depends on how complex it is: each request consumes between 1 and 10 points. A low complexity read of a single resource costs 1 point, a moderate complexity write or a read that spans multiple resources costs 3, and a complex read, an aggregation, or a batch operation costs 5 to 10. Whereby says plainly that a read-only request is not guaranteed to be a cheap one, so a lister is not automatically the frugal choice. The budget itself is set per organization, so this page will not quote a number for your account. Read it at run time instead: Whereby returns X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on responses, and a throttled call answers 429 with a Retry-After header and a body carrying the milliseconds left. A workflow that sweeps hard should pace itself from those headers rather than from an assumption.
Can an AI agent download a recording or a transcript?
It can fetch the link, and the link is the part with a catch. Whereby: Get Recording Access Link and Whereby: Get Transcription Access Link mint a temporary signed URL and return the timestamp at which it expires: one hour by default, 12 hours at most. So an agent should call the link node at the moment of download and never save the URL as a permanent address; save the recording id or transcription id instead. Both nodes change no stored state, and both cover Whereby hosted files only, since a file written to your own S3 bucket is fetched from that bucket instead.
Are Whereby session summaries included?
No. Whereby's own API reference marks the session summaries family as beta and available to selected customers, so shipping those nodes would put steps in the palette that most organizations cannot call, on shapes that are still moving. The connector stops at transcriptions, which is the input a summary is generated from: pull the transcript with Whereby: Get Transcription Access Link and summarize it with whichever AI step or assistant you already use on the canvas.
What happens if an automation deletes a meeting?
The room goes with it. Whereby: Delete Meeting is flagged destructive because it tears down the room rather than just removing a calendar style record: anyone currently in the call is removed, the room URL stops working, and a new room gets a newly generated name, so the same URL is not something you can mint again. The call is idempotent, so deleting an already deleted meeting reports the same success. Treat it the way you would any irreversible step: put it behind a condition, a retention rule, or an approval task rather than a bare trigger.
Can I report on Whereby usage day by day?
Not from the insights nodes directly, and the reason is worth knowing before you build a chart. Whereby: Get Room Insights returns one row per room, and each row's minutes, session counts, and unique participant counts are totals for that room rather than for a window you asked about. Its date filter selects which rooms are returned by when they were created rather than scoping those totals, so grouping them by date gives you minutes belonging to rooms created that day, which is a different quantity from minutes used that day. For a genuine time series, work from Whereby: Get Room Session Insights, whose rows are individual sessions with their own start and end times, and remember that an average rating cannot be summed and unique participant counts cannot be added across rows.
Put Whereby to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Whereby is a product of its respective owner; Mattering is an independent platform.