> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/daily.co.md).

# Daily.co

Run video calls with Daily.co: create and manage rooms, mint meeting tokens for private calls, and list cloud recordings through the REST API.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Daily.co  | API Key        |

#### Daily.co

Connect to Daily.co with a domain API key to create and manage video call rooms, meeting tokens, and recordings.

**Set up in Daily.co**

1. Prepare the Daily.co account or service that the workflow will access. Grant access to the required resources and operations.
2. **API Key:** Daily.co API key for your domain. Find it in the Daily.co dashboard under Developers > API keys.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Daily.co**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                    |
| ------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API Key       | Yes      | Daily.co API key for your domain. Find it in the Daily.co dashboard under Developers > API keys. [Provider instructions](https://dashboard.daily.co/developers). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Daily.co** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Create Room

Create a new video call room in Daily.co.

**Inputs**

| Field            | Type            | Required | Description                                                                |
| ---------------- | --------------- | -------- | -------------------------------------------------------------------------- |
| Room Name        | string          | No       | Name for the room (leave empty to auto-generate).                          |
| Privacy          | select (string) | No       | Who can join the room. Available values: Public, Private. Default: public. |
| Max Participants | integer         | No       | Maximum number of participants allowed in the room.                        |
| Enable Chat      | boolean         | No       | Show the chat panel in the room UI. Default: false.                        |
| Expires At       | datetime        | No       | When the room stops accepting new joins.                                   |

**Outputs**

| Field          | Type   | Description                                     |
| -------------- | ------ | ----------------------------------------------- |
| Room           | object | The created Daily.co room.                      |
| Room Name      | string | Name of the created room, for downstream nodes. |
| Room URL       | string | Join URL of the created room.                   |
| Result Message | string | Human-readable result summary.                  |

#### Get Room

Get a Daily.co room's details and join URL.

**Inputs**

| Field | Type            | Required | Description                                                                          |
| ----- | --------------- | -------- | ------------------------------------------------------------------------------------ |
| Room  | select (string) | Yes      | Select a room, or type its name manually. Options load from the selected connection. |

**Outputs**

| Field          | Type   | Description                             |
| -------------- | ------ | --------------------------------------- |
| Room           | object | The Daily.co room details.              |
| Room Name      | string | Name of the room, for downstream nodes. |
| Room URL       | string | Join URL of the room.                   |
| Privacy        | string | Privacy setting of the room.            |
| Result Message | string | Human-readable result summary.          |

#### Create Meeting Token

Create a meeting token to join a Daily.co room.

**Inputs**

| Field      | Type            | Required | Description                                                                             |
| ---------- | --------------- | -------- | --------------------------------------------------------------------------------------- |
| Room       | select (string) | Yes      | Select the room this token grants access to. Options load from the selected connection. |
| User Name  | string          | No       | Display name for the participant using this token.                                      |
| Is Owner   | boolean         | No       | Grant meeting owner privileges. Default: false.                                         |
| Expires At | datetime        | No       | When the token stops working.                                                           |

**Outputs**

| Field          | Type   | Description                      |
| -------------- | ------ | -------------------------------- |
| Meeting Token  | string | The meeting token (JWT).         |
| Room Name      | string | Room the token grants access to. |
| Result Message | string | Human-readable result summary.   |

#### List Recordings

List call recordings in your Daily.co domain.

**Inputs**

| Field          | Type            | Required | Description                                                                                |
| -------------- | --------------- | -------- | ------------------------------------------------------------------------------------------ |
| Room           | select (string) | No       | Only list recordings from this room (optional). Options load from the selected connection. |
| Limit          | integer         | No       | Maximum number of recordings to return. Default: 20.                                       |
| Starting After | string          | No       | Recording ID to start after (pagination cursor).                                           |

**Outputs**

| Field          | Type          | Description                                           |
| -------------- | ------------- | ----------------------------------------------------- |
| Recordings     | object\_array | The recordings on this page.                          |
| Recording IDs  | array         | IDs of the returned recordings, for downstream nodes. |
| Total Count    | integer       | Number of recordings returned by this call.           |
| Has More       | boolean       | Whether more recordings exist on later pages.         |
| Result Message | string        | Human-readable result summary.                        |

#### Delete Room

Permanently delete a Daily.co room.

**Inputs**

| Field | Type            | Required | Description                                                                       |
| ----- | --------------- | -------- | --------------------------------------------------------------------------------- |
| Room  | select (string) | Yes      | Select the room to delete permanently. Options load from the selected connection. |

**Outputs**

| Field          | Type    | Description                    |
| -------------- | ------- | ------------------------------ |
| Deleted        | boolean | Whether the room was deleted.  |
| Room Name      | string  | Name of the deleted room.      |
| Result Message | string  | Human-readable result summary. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/daily.co.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
