Menu

Mattering Automations Daily.co integration

Connect Daily.co to Mattering Automations: video rooms, meeting tokens, cloud recordings, stored transcripts, post-call Batch Processor jobs, live presence, meeting sessions, webhook subscriptions and domain configuration as workflow steps, authenticated with one API key.

The Mattering Automations Daily.co integration adds Daily's REST API v1 to your automation canvas: create and manage video rooms one at a time or in bulk, mint and validate meeting tokens, start and stop cloud recording and live transcription, list and download recordings and transcripts through temporary access links, queue post-call transcription and summarization through the Batch Processor, read near real time presence and completed meeting sessions, manage webhook subscriptions, set domain wide defaults, and read call quality and API request logs. One split to know 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.

The credential is a Daily API key, found in the Daily dashboard under Developers and sent as an Authorization Bearer header on every request. Two details from Daily's own documentation decide who runs this setup: only domain owners can view or regenerate the key, and a key belongs to one Daily domain, with Daily documenting that an account does not support a second domain. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference.

The safety modeling is stated on the nodes rather than buried. Of the 39 nodes, 22 read and 17 act, and five carry a destructive flag: Daily.co: Delete Room, Daily.co: Delete Recording, Daily.co: Delete Transcript, Daily.co: Delete Webhook, and Daily.co: Delete Batch Processor Job. Three of them destroy a stored file with no trash to restore from, and the webhook delete destroys information rather than a row, because Daily stops delivering immediately and never replays what happened while the endpoint was gone. Daily's API also returns webhook signing secrets inside webhook responses and recorded request bodies inside the API log, so the nodes carrying those say so in their descriptions.

Before you start

  • A Daily account with a domain, and access to its API key. Daily documents that only domain owners can view or regenerate the key, so if your team separates duties, the person connecting Daily to Mattering has to be an owner rather than a member.
  • A decision about which Daily domain this credential points at. A key belongs to one domain, and Daily documents that an account does not support a second domain, so an isolated staging environment means a separate Daily account with its own key rather than a second key here.
  • A Daily plan that covers the features your workflow needs. Daily's documentation marks cloud recording, transcription (both live and post-call) and the Batch Processor as paid plans only. On a free account the room, meeting token, presence, meeting session, webhook and domain config nodes work, while the recording, transcript and Batch Processor nodes are refused. Check your plan before building a workflow around a recording or a transcript, because the verify path below reads rooms and will pass on any valid key regardless of plan.
  • At least one room to point the first workflows at, or none at all. Rooms can be created by the integration itself with Daily.co: Create Room, so an empty domain is fine; the verify path below reads cleanly either way.
  • A Mattering workspace with access to the Automations app.
  • Not required and not stored here: meeting tokens. Those are minted per person per room by Daily.co: Create Meeting Token and consumed by whoever joins the call, so they flow through a workflow rather than living in this credential.

Get your Daily API key

Mattering authenticates to Daily with the domain's API key, sent as an Authorization Bearer header on every request to api.daily.co. Daily's own wording is that almost all of its endpoints require the key in that header, and there is no second auth mode to choose: no basic auth, no signed request, no key in a query string. There are also no scopes to select, which makes setup short and means the key carries the domain's full API access, so store it only in systems built to hold secrets.

Sign in to the Daily dashboard and open Developers.
Reveal the API key and copy it. If nothing is there to reveal, you are signed in as a member: Daily allows only domain owners to view or regenerate the key, so ask an owner to run this step or to be granted owner access first.
This key carries full API access to the Daily domain: rooms, recordings, transcripts, webhooks and domain wide configuration. Never share it publicly or commit it to version control. Regenerating it in the Daily dashboard invalidates the old key everywhere it is used at once, including this integration's credential, so plan a rotation rather than discovering it through failing workflows.
A Daily API key is not a meeting token. The key authenticates the REST API and belongs to the domain; a meeting token is a short-lived credential that lets one person into one room and is minted by a node during a workflow. Pasting a meeting token here will not authenticate anything.

Connect Daily.co to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Daily.co from the list.
Click Create new credential, paste the Daily API key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Daily's room list endpoint with a limit of one, which any valid key can read: a successful response proves the credential even on a domain with no rooms yet, and a failure carrying the error string authentication-error means the key is wrong, mistyped, or has been regenerated. Note that this probe reads rooms, which are not plan gated, so it proves the key rather than proving that recording or transcription is available on your plan.
Click Connect. All 39 Daily.co nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Daily.co section should list the query and action nodes. Drop Daily.co: List Rooms onto the canvas and run a test step. It is the integration's natural probe: it takes no required parameters, and collections come back wrapped, so the rows sit at data.data[]. Copy a room NAME rather than an id, because Daily addresses rooms by name throughout its API and every room node asks for the name.

Next, run Daily.co: Get Domain Config, which also takes no parameters and confirms the key can read domain level settings, and Daily.co: List Meetings for the sessions that have already happened. If your domain records calls, Daily.co: List Recordings completes the picture, with one note: it is rate limited harder than most endpoints, so avoid hammering it during testing. Two shape surprises are worth meeting here rather than in production: the connector maps Daily.co: List Webhooks as a BARE JSON array, so its paths start data[] rather than the data.data[] of Daily's other collections, which is also how its option pickers are wired, and Daily.co: Get Presence returns an object keyed by room name with no list at all. Everything in this verify path is read-only: it cannot reach the five destructive nodes and changes nothing, so it is safe to re-run whenever you rotate the key.

Node reference

39 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 22

Daily.co: Get Batch Processor Job

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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

dailyco_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.

Using the integration

On the automation canvas

Daily.co nodes chain with every other node: a scheduled workflow can run Daily.co: Create Room for tomorrow's sessions and write the join URLs into a Mattering database, a form submission can mint a private room plus a scoped token, and a finished recording can become a transcript, a summary and a task without a person in the loop. The value almost every downstream node asks for is the room NAME from Daily.co: List Rooms, not an id. Where an id is wanted instead, it is a different id per family: recordings, transcripts, meeting sessions, webhooks and batch jobs each have their own, and each has a lister that produces it. Two nodes work above all of that: Daily.co: Get Domain Config reads the defaults every room inherits, and Daily.co: Set Domain Config changes them for EVERY room on the account, so reach for Daily.co: Update Room when the change belongs to a single room. Only the keys you send are touched, and sending the previous values back is the way to reverse it.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. An agent can create a room with Daily.co: Create Room, mint an expiring credential with Daily.co: Create Meeting Token, watch the session with Daily.co: Get Room Presence, and once it is over queue text with Daily.co: Submit Batch Processor Job. The read nodes are the safest surface to hand an agent; keep the five destructive nodes behind conditions or approval steps, and treat token creation as a write worth gating too, since an issued token cannot be pulled back on its own.

Rooms and meeting tokens, and who gets told

Daily.co: Create Room mints a room and returns its join URL, and Daily.co: Batch Create Rooms does many at once, with the connector mapping its response as a bare array of the created rooms, so those paths start data[] too. Daily sends nothing to anyone on either call: there is no attendee list and no notification, so distributing the URL is the workflow's job. A public room can be joined by anyone with the URL. A private room needs Daily.co: Create Meeting Token, and that token deserves care: it grants entry, an owner token can also record the call and remove participants, 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. Each of those hits far more than the single token, which is why the expiry is the real control. Always set an expiry, and always set the room name, because a token minted without one is valid for every room on the domain. Daily.co: Validate Meeting Token can inspect a token, with the caveat its description carries: the token travels in the URL path, so it lands in the node's stored configuration and in Daily's own API logs. Prefer passing it from an upstream node over pasting it in.

Recording and transcription: accepted is not finished

Daily.co: Start Recording, Daily.co: Stop Recording, Daily.co: Start Transcription and Daily.co: Stop Transcription all act on a session that is already running, and all four return an acceptance rather than an artifact. The pattern is to poll: Daily.co: List Recordings or Daily.co: Get Recording until the status turns from in-progress to finished, Daily.co: List Transcripts or Daily.co: Get Transcript until a transcript reads t_finished. Two prerequisites live in the room rather than in the node: a recording mode has to be set on the room or the joining token for a start to do anything, and transcription storage has to be enabled for a live transcript to be saved rather than shown as captions and discarded. A stop is not a pause: a later start begins a new recording rather than resuming the old one, and nothing captured so far is deleted.

Access links expire, so fetch them last

Three nodes mint temporary download URLs: Daily.co: Get Recording Access Link, Daily.co: Get Transcript Access Link and Daily.co: Get Batch Processor Job Access Link. None of them change anything, which is why they are query nodes, but all three produce something perishable and sensitive. In practice the recording link node returns its expiry as a unix timestamp on data.expires, so read that value rather than assuming a lifetime, while the transcript link carries its expiry inside the signed URL itself. Neither node takes a parameter for the lifetime, so a workflow should call these at the moment it is about to download or send, never at the start of a long run and never into a stored field. Anyone holding one of these URLs can read the media until it expires.

Post-call processing with the Batch Processor

Daily.co: Submit Batch Processor Job queues transcription or summarization of a recording or media file and returns a job id, because the work is asynchronous. Daily.co: Get Batch Processor Job is the poll, moving through submitted and processing to finished or error, and it returns the storage locations of the outputs rather than the outputs themselves, which is why the access link node is separate. Daily.co: List Batch Processor Jobs is deliberately thin, carrying only id, preset and status. The transcript preset produces txt, srt, vtt and json and is performed by Deepgram, the same third party behind live transcription. Daily.co: Delete Batch Processor Job removes the job and, as the node's own description records, the files it produced when those files live in Daily's bucket, but NOT objects written to a bucket you own, which is why its response still echoes the output locations: that is the list you need to clean up yourself.

Webhooks, and the subscription list that replaces itself

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, and Daily begins POSTing immediately, so have the receiver ready before running the node. The response carries the hmac signing secret used to verify deliveries, and so do Daily.co: List Webhooks and Daily.co: Get Webhook, which is why all three warn that their output is sensitive. The behaviour that catches people: sending event types to Daily.co: Update Webhook REPLACES the whole subscription list rather than extending it, so read the current set first. And a lookup quirk the connector records rather than guesses at: the single webhook lookup can come back wrapped in an array, so handle both data.uuid and data[0].uuid, and source webhook ids from the lister, where the shape is not in doubt.

Sessions, presence and logs, read for what they are

Daily.co: List Meetings returns meeting sessions newest first, and each row is an EVENT at its own timestamp rather than a bucket in a usage report: there is no grouping parameter, a row flagged ongoing has a duration that is still growing while a participant remains, and its peak participant count belongs to that one session and is never the number of people on the domain at once. Daily.co: Get Meeting fetches one session by id and Daily.co: List Meeting Participants opens it up person by person. For the present tense use presence instead: Daily.co: Get Presence across the domain or Daily.co: Get Room Presence for one room, both near real time with a delay of up to 15 seconds and both asked to be polled no more often than that. Daily.co: List Logs carries call quality logs and metric samples for debugging what one caller experienced, and its own start and end parameters are documented on the node in JavaScript milliseconds, while rooms and meetings use unix seconds, which is exactly the mix-up that silently returns an empty window. Daily.co: List API Logs is the other log: an audit trail of the REST calls made against the domain and the webhook deliveries Daily attempted, with status codes and the recorded request and response bodies, which makes it the fastest way to see why an automation's call was refused and also a reason to treat that node's output as sensitive.

What stays off the canvas

Four boundaries are deliberate. Telephony (dial-in, dial-out, SIP transfer, and buying or releasing phone numbers) places real calls to real numbers and provisions billable resources that Daily's own API says cannot be released for 14 days after purchase, so a mistake is not undoable for two weeks. Live streaming needs an RTMP ingest URL and key belonging to another service, and this API has no lister and no access link to read a stream back afterwards, so a workflow could start one and never see it again. In-call session controls, such as ejecting a participant, changing permissions or sending an app message, address a call that is already running, belong to Daily's client library, and reach people in a way no undo covers. And Daily's bulk room delete is omitted because this build could not establish which rooms the call selects: a destructive bulk call whose scope is unclear is not something to guess at. The single room delete IS here, and so is bulk room creation.

Troubleshooting

Test Connection fails with an authentication error
Daily answers with the error string authentication-error when the Authorization header carries a key it does not recognise, so a failure here is about the credential itself rather than permissions. Check for leading or trailing whitespace from the copy, and confirm the key was not regenerated in the Daily dashboard after you saved it, because regeneration invalidates the old key immediately. Copy the key again from Developers and update the credential in Connectors. If you pasted a meeting token by mistake, this is what it looks like: tokens authenticate a person into a room, not the REST API.
A call fails with authorization-header-error rather than authentication-error
Those two are different failures and Daily separates them. authentication-error means a key was sent and Daily rejected it, so the credential is the thing to fix. authorization-header-error means the Authorization header was missing or badly formatted, which points at the request rather than at the key: a node running before a credential was attached, a hand-built HTTP step that did not carry the header, or one that carried it in the wrong shape. Attach the Daily.co credential to the node and run it again. The distinction also matters when you want to test an auth failure on purpose: send a deliberately wrong key, because sending no key at all produces the header error instead of the authentication error.
A room node returns 404 even though the room is in the list
Daily addresses rooms by NAME, not by id, everywhere in its path space. If a workflow carried the id from a room row into Daily.co: Get Room, Daily.co: Update Room or Daily.co: Delete Room, the picker will have looked perfect and every call will 404. Map the name field from Daily.co: List Rooms instead. The one place the room UUID is wanted is the transcripts filter, which asks for a room id rather than a name, so the two are offered separately in the pickers for exactly this reason.
Start Recording returned 200 but no recording exists
The 200 means Daily accepted the instruction, and the response body reads status sent rather than describing a file. Two things commonly stop a file appearing. First, the room or the joining token has to have a recording mode set before a start does anything, so check the room configuration with Daily.co: Get Room and set it with Daily.co: Update Room. Second, there has to be a session actually running: these nodes act on a live call, not on an empty room. Once the recording is genuinely running, poll Daily.co: List Recordings until a row appears and its status turns from in-progress to finished; the file only exists at that point.
A download link that worked yesterday now returns an error
Access links are temporary by design and none of the three nodes takes a parameter to extend them. In practice Daily.co: Get Recording Access Link returns its expiry as a unix timestamp on data.expires, and the transcript and batch job links carry their expiry inside the signed URL itself, so a link stored in a database or pasted into a task is already on its way to being dead. The fix is a workflow pattern rather than a setting: call the access link node at the moment of download or delivery, treat the URL as single use, and store the recording or transcript ID instead, since that never expires. Treat any link you do send as sensitive, because it grants access until it expires.
A Batch Processor job never finishes, or its access link returns 400
The job runs asynchronously, so a submit returns only an id and the status has to be polled with Daily.co: Get Batch Processor Job through submitted and processing to finished. A 400 from Daily.co: Get Batch Processor Job Access Link is what the node records for a job that has not finished, so poll before minting links. A 404 from the same node means the job id does not exist. If the job reaches the error status, its record carries an error string describing why, and the source recording is untouched, so a corrected job can be resubmitted against the same recording.
Events stopped arriving at a webhook endpoint
Check the webhook record first with Daily.co: List Webhooks, which reports each endpoint's retry mode and its count of consecutive failures alongside the time an event was last pushed: a rising failure count says Daily is trying and your receiver is refusing. If the subscription itself looks wrong, remember that sending event types to Daily.co: Update Webhook replaces the whole list rather than adding to it, so an update meant to add one event can silently unsubscribe the rest. And if the endpoint was deleted, the gap cannot be recovered: Daily stops delivering immediately and does not replay events that occurred while it was gone, so recreate it and backfill from Daily.co: List Meetings or Daily.co: List Recordings for the window you lost.
Requests start failing with 429 during a bulk run
Daily documents its rate limits in tiers, and describes the two tighter ones as approximate, so treat them as guidance: roughly 20 requests per second or 100 across a 5 second window for most endpoints, roughly 2 per second or 50 across 30 seconds for deleting a room and listing recordings, and roughly 1 per second or 5 across 5 seconds for starting a recording, a live stream or a phone call. A throttled call comes back as 429 with the error string rate-limit-error, and Daily asks for exponential backoff. In practice that means spacing a bulk sweep out rather than fanning it wide, and preferring Daily.co: Batch Create Rooms over a loop of single creates.
A meetings or logs query returns nothing for a window that should have data
Daily uses two different time units in one API, which is the usual cause. Rooms, meeting tokens and meeting sessions use unix SECONDS, while Daily.co: List Logs takes its window in JavaScript MILLISECONDS, which is how the node's own start and end parameters are defined, so a value copied from one into the other lands thousands of years away and returns an empty result. Two smaller causes worth checking: Daily generally does not record a join until someone has stayed about 10 seconds, so very short test calls may not appear at all, and Daily.co: List Logs requires one of a meeting session id or a user session id, returning its own 400 when given neither.
A whole family of endpoints returns forbidden-error while others work
Daily's documented error strings include forbidden-error, which is a different failure from authentication-error: the key was recognised and the specific operation was refused. Start with the plan, which is the common cause. Daily's documentation marks cloud recording, transcription (live and post-call) and the Batch Processor as paid plans only, so on a free account exactly those families are refused while rooms, meeting tokens, presence, meetings, webhooks and domain config keep working, which is the pattern of one family failing while the rest pass. Test Connection will not catch this, because it reads rooms, which are not plan gated. If the plan already covers the feature, the secondary case is a per domain setting or a precondition: check with Daily whether that capability is enabled for your domain, and check the node's own description, since several families carry one, recording needs a recording mode on the room, saved live transcripts need transcription storage enabled, and the batch job access link refuses a job that has not finished.

Daily.co is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products