Menu
Mattering Automations connector

A Daily.co MCP for calls that keep working after the call ends

Connect one Daily API key and rooms, meeting tokens, cloud recordings, transcripts, post-call processing jobs, live presence and webhook subscriptions become workflow steps. An AI agent can mint a room and a scoped token, a workflow can start and stop a recording on a timer, and the transcript and summary can land next to your tasks and databases instead of in a dashboard tab.

39 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Daily.co MCP connector does

The Daily.co connector for Mattering Automations is 39 nodes on Daily's REST API v1: rooms from creation through update and delete plus bulk creation, meeting tokens with validation, cloud recordings with metadata and temporary download links, stored transcripts, post-call Batch Processor jobs for transcription and summarization, live and stopped control of recording and transcription, near real time presence for the domain or one room, meeting session analytics with per participant detail, webhook subscriptions, domain wide configuration, and call quality and API request logs. One API key, sent as an Authorization Bearer header, 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 create a room, mint a meeting token that expires, watch for the session to finish, queue a transcript and a summary, and hand back a download link, without anyone opening the Daily dashboard.

Daily's own developer surface is split in two, and it is worth knowing which half this is. Behaviour inside a live call belongs to Daily's client libraries running in the browser or the app: joining, muting, ejecting, sending messages between participants. This connector is the other half, the REST control plane: the resources that exist before a call starts and the artifacts that exist after it ends. That is the half a workflow can actually own, which is why the node list leans on rooms, tokens, recordings, transcripts, jobs and webhooks rather than on in-call controls.

The safety modeling is stated plainly. Of the 39 nodes, 22 read and 17 act, and five are flagged destructive: room, recording, transcript, webhook and batch job deletes. Three of those take a file or a stream of information with them, and the node descriptions say so rather than leaving it to be discovered. Scope is stated honestly too: the telephony family (dial-in, dial-out, phone number purchase and SIP transfer), live streaming, in-call session controls and Daily's bulk room delete are deliberately not here, each for a reason given in the FAQ below. And because Daily returns webhook signing secrets inside webhook responses, and recorded request bodies inside API logs, the nodes that carry them say so in their descriptions so you treat their output accordingly. One more split worth knowing before you build: Daily's documentation marks cloud recording, transcription (live and post-call) and the Batch Processor as paid plans only, while rooms, meeting tokens, presence, meeting sessions, webhooks, domain configuration and logs carry no such badge, so a free account can run the second group and will be refused on the first.

One connection, three surfaces

  • Visual automations. Drag Daily.co 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 Daily.co node, ready to drop on the canvas

39 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 22

Daily.co: Get Batch Processor Job

Fetch one post-call processing job: its status, the input it was given, the bucket, region and key of every file it produced, and an error string when the status is error. This is the node to poll after submitting a job. It returns the STORAGE LOCATIONS of the outputs, not the files: use Daily.co: Get Batch Processor Job Access Link to download them.

Daily.co: Get Batch Processor Job Access Link

Mint temporary download URLs for a finished job's outputs: one link per transcript format (txt, json, srt and vtt) and one for the summary. THE LINKS EXPIRE, so fetch them at the moment you are about to download rather than storing them, and treat them as sensitive since anyone holding one can read the content. Daily returns 400 if the job has not finished and 404 if the job id does not exist. Nothing is changed by this call.

Daily.co: Get Domain Config

Read the domain's own name and id plus its top level configuration, which every room inherits unless the room or a meeting token overrides it. Takes no parameters. The path is the bare root of the API base, so this is a real endpoint rather than a placeholder.

Daily.co: Get Meeting

Fetch one meeting session by id: its room, start time, duration in seconds, peak participant count and whether it is still running. Use Daily.co: List Meeting Participants for who was in it.

Daily.co: Get Presence

Near real time snapshot of everyone currently in a call anywhere on the domain, with a delay of up to 15 seconds. Takes no parameters. THE SHAPE IS UNUSUAL: the response is an object KEYED BY ROOM NAME whose values are participant arrays, so there is no data list to walk generically and a consumer has to iterate the keys. Daily asks that this be polled no more often than once every 15 seconds. Use this rather than Daily.co: List Meetings when you need the current state of a room.

Daily.co: Get Recording

Fetch one recording's metadata by id: status, duration, peak participant count, S3 key and the meeting session id it came from. Poll this after starting a recording to learn when the status turns from in-progress to finished.

Daily.co: Get Recording Access Link

Mint a temporary download URL for a recording, together with the unix timestamp at which it stops working. THE LINK EXPIRES: data.expires is the exact expiry, so read it rather than assuming a duration, fetch the link at the moment you are about to download, and never store it as a permanent address. Daily documents no parameter for changing the lifetime. Treat the link itself as sensitive: anyone holding it can download the recording until it expires. Nothing is deleted or changed by this call.

Daily.co: Get Room

Fetch one room by name, including its join URL, privacy, creation time and the config object holding whatever room properties are set on it.

Daily.co: Get Room Presence

Near real time snapshot of who is currently in ONE room, with each person's participant id, join time, elapsed duration in seconds and meeting session id, plus the user_id and user_name that came from their meeting token. Unlike the domain wide presence node, this one returns the usual total_count and data list. Delay is up to 15 seconds.

Daily.co: Get Transcript

Fetch one transcript's metadata by id, including its status, which is what tells you whether the file is ready, and outParams, which names the bucket, region and key the file was written to.

Daily.co: Get Transcript Access Link

Mint a temporary download URL for a transcript file. THE LINK EXPIRES: the expiry is carried inside the signed URL itself, so fetch the link at the moment you are about to download rather than storing it, and treat a stored link as already dead. Treat the link as sensitive, since anyone holding it can read the transcript. Nothing is changed by this call.

Daily.co: Get Webhook

Fetch one webhook endpoint by id, including its subscribed events, retry mode, consecutive failure count and the time an event was last pushed to it. Daily's published spec declares this response as an ARRAY even though it is a single lookup, which is most likely a defect in their spec rather than the wire format, so handle both data.uuid and data[0].uuid. The response carries the hmac signing secret, so treat this node's output as sensitive.

Daily.co: List API Logs

Audit trail of REST API calls made against the domain and of webhook deliveries Daily attempted, each with the method, path, status code, caller IP, and the request and response bodies as strings. Useful for finding out why an automation's call was rejected. Returns a BARE JSON ARRAY, so paths start data[]. Note that recorded request and response bodies can contain whatever was sent, so treat this node's output as sensitive.

Daily.co: List Batch Processor Jobs

List post-call processing jobs with their id, preset and status (submitted, processing, finished or error). This listing is deliberately thin: use Daily.co: Get Batch Processor Job for a job's inputs and output file locations.

Daily.co: List Logs

Call quality logs and metric samples for one meeting session or one participant, for debugging what a caller actually experienced. ONE OF mtgSessionId OR userSessionId IS REQUIRED: supplying neither returns Daily's own 400. The response is shaped {"logs": [...], "metrics": [...]}, and each array only appears when its include flag is set. Note the timestamps here are JavaScript MILLISECOND timestamps, unlike the second based ones on rooms and meetings.

Daily.co: List Meeting Participants

List who was in one meeting session, with each person's join time, how long they stayed in seconds, their participant id, and the user_id and user_name that came from their meeting token. user_id and user_name are null when no token supplied them, which is the normal case for a public room. This response carries data without a total_count.

Daily.co: List Meetings

List meeting SESSIONS newest first with their start time, duration in seconds, peak participant count, whether they are still running, and the participants who joined. A session is a set of people in a room together over one time window, so a reused room has many sessions and one person's unbroken time in a room can span several. Timestamps are unix seconds with roughly 15 second granularity, and Daily generally does not record a join until someone has stayed at least 10 seconds. For the CURRENT state of a room use Daily.co: Get Presence instead, which is near real time.

Daily.co: List Recordings

List cloud recordings newest first with their status (in-progress or finished), duration in seconds, start timestamp, peak participant count, S3 key and the meeting session they came from. This is METADATA ONLY: use Daily.co: Get Recording Access Link to get something downloadable. This endpoint is rate limited harder than most (about 2 requests per second).

Daily.co: List Rooms

List the domain's rooms newest first with their name, privacy, join URL, creation time and configuration. Also the connector's auth probe: it needs no parameters, and a request carrying an invalid key returns 401 authentication-error while a request with no Authorization header at all returns 400 authorization-header-error.

Daily.co: List Transcripts

List stored transcripts newest first with their status (t_in_progress, t_finished or t_deleted), duration in seconds, room id, meeting session id and timestamps. Metadata only: use Daily.co: Get Transcript Access Link for the file. These are transcripts saved from LIVE transcription; post-call jobs live under the Batch Processor nodes instead. Note the rows carry a room UUID rather than a room name.

Daily.co: List Webhooks

List the domain's webhook endpoints with their id, target URL, subscribed event types, retry mode, consecutive failure count and timestamps. Returns a BARE JSON ARRAY, so paths start data[] rather than the data.data[] of Daily's other collections. Each row also carries the hmac signing secret for that endpoint, so treat this node's output as sensitive.

Daily.co: Validate Meeting Token

Check a meeting token and return the properties encoded in it, including which room it grants access to and whether it carries owner privileges. Nothing is created or changed. Note that the token travels in the URL PATH, so it will appear in this node's stored configuration and in Daily's own API logs; prefer passing it from an upstream node rather than pasting it in.

Action nodes 17

Daily.co: Batch Create Rooms

Create many rooms in one call and get the created room objects back as a bare JSON ARRAY, so paths start data[] rather than data.data[]. Each entry takes the same name, privacy and properties shape as Daily.co: Create Room. Reversible one room at a time with Daily.co: Delete Room; the matching bulk DELETE is not offered by this connector because Daily documents no selector for it.

Daily.co: Create Meeting Token

Mint a meeting token, which is returned at data.token. TREAT THE RETURNED TOKEN AS A SECRET: it is a signed credential that GRANTS ENTRY to a room, so anyone who obtains it can join, and an is_owner token can additionally record the call and remove other participants. Daily provides no way to revoke an issued token, so bound it with exp and set room_name, or the token is valid for EVERY room on the domain. Nothing is emailed and nobody is notified; delivering the token is the caller's job, and it should never be logged or pasted into a shared surface. Reversible in the sense that nothing is created or changed on the domain, but an issued token cannot be withdrawn before it expires.

Daily.co: Create Room

Create a video room and return its join URL. The API takes no attendee list and Daily documents no invitation or notification on this call, so nothing is sent to anyone: distributing data.url is the caller's job. A public room can be joined by anyone holding the URL; a private room additionally needs a meeting token or the knocking lobby. Reversible by Daily.co: Delete Room.

Daily.co: Create Webhook

Register a webhook endpoint and subscribe it to a set of Daily events. The response carries the hmac signing secret used to verify deliveries, so treat this node's output as sensitive; if you do not supply one, Daily provisions it and returns it. Daily starts POSTing events to the URL immediately, so have the receiver ready first. Reversible by Daily.co: Delete Webhook.

Daily.co: Delete Batch Processor Job

Destructive and irreversible: delete a post-call processing job AND the files it produced, when those files live in Daily's own bucket. Objects written to a custom bucket are NOT deleted, which is why the response still echoes the output locations: that is the information you need to clean up your own bucket yourself. The source recording is left alone, so a job can be resubmitted while the recording survives.

Daily.co: Delete Recording

Destructive and irreversible: delete a recording and its stored file. There is no undo and no trash to restore from, and a recording cannot be regenerated because the call it came from is over. The response echoes the S3 bucket, region and key that were removed.

Daily.co: Delete Room

Destructive and irreversible: delete a room. The join URL stops working and anyone in the call loses the room. Creating a room with the same name afterwards produces a NEW room with a new id, not the old one. Recordings and transcripts already produced from the room survive and stay reachable by id. This endpoint is rate limited harder than most (about 2 requests per second).

Daily.co: Delete Transcript

Destructive and irreversible: delete a transcript and its stored file. There is no undo. A live session transcript cannot be regenerated at all, though a NEW transcript can be produced from a surviving recording with Daily.co: Submit Batch Processor Job. The response echoes the record with its status set to t_deleted.

Daily.co: Delete Webhook

Destructive and irreversible: delete a webhook endpoint. Daily stops delivering events to it immediately and events that occur while it is gone are NOT replayed later, so anything your receiver would have learned in that window is lost. Recreating it mints a new id and, unless you supply one, a new signing secret. Returns 200 with no body.

Daily.co: Set Domain Config

Change the domain wide defaults every room inherits. THIS AFFECTS THE WHOLE DOMAIN, not one room, so a mistake here changes behaviour for every call your account runs; prefer Daily.co: Update Room when the change belongs to one room. Only the keys you send are touched. Reversible by sending the previous values back, which Daily.co: Get Domain Config returns under data.config. Daily documents hipaa and intercom_auto_record as read only through this endpoint.

Daily.co: Start Recording

Start a cloud recording in a room that has a session running. The 200 means the instruction was ACCEPTED (the body is {"status": "sent"}), not that a file exists: poll Daily.co: List Recordings until a row appears and its status turns from in-progress to finished. The room or the joining token must already have a recording mode set, or nothing starts. Reversible by Daily.co: Stop Recording, and the resulting file is deletable. Recording consumes metered media processing for as long as it runs, so set maxDuration rather than relying on someone remembering to stop it. This endpoint is rate limited hard (about 1 request per second).

Daily.co: Start Transcription

Start live transcription in a room that has a session running. The 200 means the instruction was accepted, not that a transcript exists. The room needs enable_transcription_storage set for the result to be SAVED; without it the captions are live only and nothing lands in Daily.co: List Transcripts. Transcription is performed by Deepgram, so the language and model values follow Deepgram's own vocabulary. Reversible by Daily.co: Stop Transcription. Live audio is sent to a third party processor for as long as this runs, which is worth stating to participants.

Daily.co: Stop Recording

Stop the recording running in a room. The 200 means the instruction was accepted; the file finishes processing afterwards, so poll Daily.co: List Recordings until its status is finished. Nothing is deleted: the recording made so far is kept and stays downloadable. Reversible in the sense that Daily.co: Start Recording begins a NEW recording, not a resumption of this one.

Daily.co: Stop Transcription

Stop live transcription in a room. The 200 means the instruction was accepted. Nothing is deleted: if the room had transcription storage enabled, the transcript captured so far is kept and appears in Daily.co: List Transcripts. Reversible in the sense that Daily.co: Start Transcription begins a NEW transcription rather than resuming this one.

Daily.co: Submit Batch Processor Job

Queue post-call processing of a recording or a media file and get back only a job id: the work happens asynchronously, so poll Daily.co: Get Batch Processor Job until its status turns from submitted through processing to finished (or error). The transcript preset produces txt, srt, vtt and json outputs and is performed by Deepgram; the summarize preset produces a text summary. This is the POST CALL path, distinct from the live transcription nodes. Reversible by Daily.co: Delete Batch Processor Job, which also removes the generated files when they live in Daily's own bucket.

Daily.co: Update Room

Change an existing room's privacy and configuration properties. Only the keys you send are touched, so this is a partial update rather than a replacement. Reversible by sending the previous values back, which Daily.co: Get Room returns under data.config. Two properties are documented as not changeable once a session has started: enable_screenshare and the room's recording mode take effect on the next session.

Daily.co: Update Webhook

Change a webhook endpoint's target URL, subscribed events, retry mode or credentials. Sending eventTypes REPLACES the whole subscription list rather than adding to it, so read the current set with Daily.co: Get Webhook first if you mean to extend it. Reversible by sending the previous values back. The response carries the hmac signing secret.

Connecting Daily.co takes one credential

Daily authenticates almost every REST endpoint with a single API key, sent as an Authorization Bearer header on every request. The key lives in the Daily dashboard under Developers. Two details from Daily's own documentation shape who can do this setup: only domain owners can view or regenerate the key, so a member account will not find it, and a key belongs to one Daily domain, with Daily documenting that an account does not support a second domain. A separate staging environment therefore means a separate Daily account with its own key rather than a second key on the same one.

1

Sign in to the Daily dashboard and open Developers to reveal and copy the API key. If the section shows nothing to copy, you are signed in as a member rather than a domain owner.

2

In Mattering Automations, open Connectors, click Add Connector, choose Daily.co, and create a credential with the API key.

3

Click Test Connection. Mattering calls Daily's room list endpoint with a limit of one, which any valid key can read: a response proves the credential even on a domain with no rooms yet. A failure carrying the error string authentication-error means the key itself is wrong or was regenerated, while authorization-header-error means the Authorization header was missing or badly formatted rather than the key being bad.

4

All 39 Daily.co nodes appear in the canvas palette. Run Daily.co: List Rooms first: Daily addresses rooms by NAME rather than by id, so the name in each row is the value every room node wants.

Common uses for the Daily.co MCP

Rooms and scoped tokens minted by a workflow

Daily.co: Create Room stands up a video room and returns its join URL, and Daily.co: Batch Create Rooms does a whole cohort in one call. The honest part is what does not happen: Daily takes no attendee list on the create call and sends nothing to anyone, so distributing the URL is your workflow's job, which is also what makes it composable with email, Slack or a task. For a private room, Daily.co: Create Meeting Token mints the credential that lets a specific person in. Treat that token like a password: it grants entry, an owner token can record the call and remove people, and there is no targeted revoke. Daily documents two blunt ones: delete the room a Daily-signed token was scoped to, or regenerate the API key behind a self-signed one. Both reach far past the single token you wanted gone, which is exactly why the expiry matters, so always set an expiry and always set the room name, since a token with no room name works on every room on the domain.

Recording that starts, stops and cleans up after itself

Daily.co: Start Recording begins a cloud recording in a running session and Daily.co: Stop Recording ends it, with one caveat the nodes state up front: the 200 means the instruction was accepted, not that a file exists. The workflow pattern is to poll Daily.co: List Recordings or Daily.co: Get Recording until the status turns from in-progress to finished, then call Daily.co: Get Recording Access Link when you are actually ready to download, because the link expires and the response carries the exact expiry timestamp to read rather than guess. Set maxDuration on the start rather than relying on someone remembering to stop the recording.

Post-call transcripts and summaries without a human step

Daily's Batch Processor turns a finished recording into text. Daily.co: Submit Batch Processor Job queues the work with a transcript preset (txt, srt, vtt and json outputs, produced by Deepgram) or a summarize preset, and returns only a job id, because the work is asynchronous. Daily.co: Get Batch Processor Job is the poll, and it returns the storage LOCATIONS of the outputs rather than the files, which is why Daily.co: Get Batch Processor Job Access Link exists separately to mint the download URLs. This is the post-call path and it is distinct from live captioning: Daily.co: Start Transcription is the one that runs during the call.

Webhook subscriptions managed from the same canvas that receives them

Daily.co: Create Webhook registers an HTTPS endpoint and subscribes it to Daily events such as meeting.started, meeting.ended, recording.ready-to-download and transcript.ready-to-download, so a Mattering workflow can be the receiver of the events its neighbours act on. The response carries the hmac signing secret used to verify deliveries, which is exactly why the node warns that its output is sensitive. Two behaviours worth designing around: Daily.co: Update Webhook REPLACES the event subscription list rather than adding to it, so read the current set first, and Daily.co: Delete Webhook stops delivery immediately with no replay of anything that happens while the hook is gone.

Session records that land in a database instead of a dashboard

Daily.co: List Meetings returns meeting sessions newest first with start time, duration, peak participant count and whether the session is still running, and Daily.co: List Meeting Participants opens one of them up person by person. Read the shape honestly: these are session EVENTS at their own timestamps, not a tidy per-day usage breakdown, there is no bucketing parameter, a session flagged ongoing has a duration that is still growing, and the peak participant count belongs to that one session rather than to the domain. A scheduled sweep can still write every session into a Mattering database and let the reporting happen there, which is the right place to decide how sessions roll up.

Knowing who is in a call right now

Daily.co: Get Presence is the domain wide snapshot and Daily.co: Get Room Presence narrows it to one room with each person's join time, elapsed duration and the identifiers their meeting token carried. Both are near real time with a delay of up to 15 seconds, and Daily asks that presence be polled no more often than every 15 seconds. One shape warning that saves an afternoon: the domain wide response is an object keyed by ROOM NAME rather than a list, so a consumer iterates the keys, while the single room node returns the usual list. Presence answers what is happening now; the meetings nodes answer what happened.

Example: A call ends and the transcript, summary and follow-up task write themselves

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Setup, run once: Daily.co: Create Webhook subscribes an inbound Mattering webhook URL to recording.ready-to-download, and the signing secret from the response is stored so deliveries can be verified.

2

Trigger: Daily posts the event when the recording finishes processing, and the workflow starts with the recording id in hand.

3

Daily.co: Get Recording confirms the status is finished and reads the duration and the meeting session the recording came from.

4

Daily.co: Submit Batch Processor Job queues transcription and summarization of that recording and returns a job id.

5

Daily.co: Get Batch Processor Job polls until the status moves through processing to finished, or reports the error string if it does not.

6

Daily.co: Get Batch Processor Job Access Link mints download URLs for the transcript formats and the summary at the moment they are needed, because those links expire.

7

The workflow creates a task in Mattering Productivity with the summary in the description and the session detail from Daily.co: List Meeting Participants attached, so the follow-up lands next to the rest of the work.

Daily.co MCP questions, answered

What Daily.co operations are supported?

39 nodes on Daily's REST API v1: 22 query nodes and 17 action nodes. Rooms (list, get, create, update, delete, and bulk create), meeting tokens (create and validate), cloud recordings (list, get, temporary access link, delete), stored transcripts (list, get, access link, delete), Batch Processor jobs for post-call transcription and summarization (submit, list, get, access link, delete), live control of recording and transcription (start and stop for each), presence for the whole domain or one room, meeting sessions and their participants, webhook subscriptions (list, get, create, update, delete), domain configuration (read and set), and call quality logs plus the API request audit log. Deliberately not included: the telephony surface, live streaming, in-call session controls, and Daily's bulk room delete.

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.

Can an AI agent create a room and invite people to it?

It can create the room, and inviting is a separate step you control. Daily.co: Create Room takes no attendee list and Daily documents no invitation, email or notification on that call: it mints a URL and hands it back. So the agent creates the room, and the workflow decides who receives the URL, whether that is an email node, a Slack message or a task. For a private room the agent also needs Daily.co: Create Meeting Token, and that token is a credential rather than a link: anyone holding it can join, an owner token can additionally record the call and remove participants, and there is no targeted way to pull one back. The two revocations Daily documents are blunt: delete the room a Daily-signed token was scoped to, or regenerate the API key behind a self-signed one, and each takes far more than that one token with it. Bound it with an expiry and a room name every time.

What are Daily's API rate limits?

Daily documents these limits in tiers, and describes the two tighter ones as approximate, so treat them as guidance rather than a contract. Most endpoints allow roughly 20 requests per second or 100 across a 5 second window. Deleting a room and listing recordings are limited harder, at roughly 2 per second or 50 across a 30 second window. Starting a recording, a live stream or a phone call is the tightest, at roughly 1 per second or 5 across a 5 second window. When Daily throttles, it answers 429 with the error string rate-limit-error and asks callers to back off exponentially. The node reports the error on its output rather than retrying silently, so a workflow can wait and continue.

Can a workflow record a call and get the file?

Yes, in two steps, and the split is deliberate rather than awkward. Daily.co: Start Recording and Daily.co: Stop Recording control the recording, and both return an acceptance rather than a file: the media finishes processing afterwards. Daily.co: List Recordings and Daily.co: Get Recording report the status, and only once it reads finished does a file exist. Daily.co: Get Recording Access Link then mints a temporary download URL. Those links expire, the node takes no parameter for setting the lifetime, and in practice the response carries the expiry as a unix timestamp on data.expires, so read that value rather than assuming a duration and fetch the link at the moment of download rather than storing it. One prerequisite the node states: the room or the joining token must already have a recording mode set, or the start call does nothing.

Does it transcribe calls, and where does the audio go?

Both live and post-call, through different nodes. Daily.co: Start Transcription runs during the call, and the room needs transcription storage enabled for anything to be saved: without it the captions are live only and nothing appears in Daily.co: List Transcripts. Daily.co: Submit Batch Processor Job is the post-call route, producing txt, srt, vtt and json transcripts or a summary from a finished recording. In both cases Daily states that the transcription is performed by Deepgram, so audio is processed by a third party, which is worth telling participants and worth checking against your own data commitments before you automate it.

Can I use this for usage reporting?

You can collect the raw sessions, and the honest answer is that they are events rather than a per-day usage breakdown. Daily.co: List Meetings takes a start and end window in unix seconds and returns one row per meeting session at its own arbitrary timestamp. There is no bucketing parameter, so nothing groups the rows for you. Two traps the connector documents rather than papering over: a session flagged ongoing keeps growing while a participant remains, so a figure computed today can change later, and the peak participant count on a row is the peak for that single session, never the number of people on the domain at once. Write the sessions into a Mattering database and do the rolling up there, where the choices are visible.

What is not covered, and why?

Four families are left out on purpose. Telephony (dial-in, dial-out, SIP transfer, and buying or releasing phone numbers) places real calls to real numbers and provisions billable resources, and Daily's own API states that a newly purchased number cannot be released for 14 days, so a mistake is not undoable. Live streaming needs an RTMP ingest URL and key belonging to another service, and this API offers no lister and no access link to read a stream back afterwards. In-call session controls such as ejecting a participant or sending an app message reach people inside a live call in a way no undo covers, and they belong to Daily's client library rather than to a workflow. And the bulk room delete is omitted because this build could not establish which rooms the call would select, and a destructive bulk call whose scope is unclear is not one to ship on a guess. Each of these can be added on request now that the pattern is established.

39 nodes waiting on the canvas

Put Daily.co 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. Daily.co is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products