We use necessary features to run the website and platform. With your permission, we also measure usage and performance and use marketing cookies for advertising and remarketing. Your choice applies in this browser across the website, signup and platform. Cookie policy
Closing this notice or pressing Esc lets you continue with necessary features only.
Connect Daily to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.
Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.
11 ACTIONS
published by the vendor; the company enables only the necessary ones
0 EVENTS
triggers the system can send, when the vendor offers them
API KEY
each person signs in with their own credential, encrypted
APPROVAL BY RISK
sensitive actions show a card before running
Live proof
One request, one query in Daily and one approval.
The scene shows the path of a request; the exact actions depend on the functions your company enables in Daily.
Input
A team member asks, in the conversation, for something that today requires opening Daily — inside their area's space, with their login.
What Skyller does
01Picks, among the enabled functions, a query action and looks the information up in Daily with the person's own credential.
02If the request requires writing something in Daily, acts within permission; if the function is sensitive, it first shows the card and waits for Approve.
03Returns the result in the conversation and records who asked, which action was used and when.
Result
Daily stops being an open tab and starts answering inside the conversation — through the functions your company enabled.
Good to know
The available actions are the ones the vendor publishes for Daily; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.
Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.
Where this helps your work
Daily inside the conversation where the work happens.
Three common situations for people who use Daily every day. What Skyller does in each one depends on the functions your company turns on.
Needing to know what was agreed
“What did they decide in the project channel yesterday?”
The person asks and Skyller reads the channel in Daily with their login, only in the channels they belong to, and summarizes what was agreed.
Channel summary in the conversation
Notifying the team
“Tell the team the new policy has been published.”
Posting a message is a write action; with the function set to ask for approval, Skyller shows the card with channel and text and only sends it in Daily after Approve.
Message with approval
Administering
“A tool is one thing. A conversation channel is another.”
Here Daily is a tool: the AI reads and writes in it through the enabled functions. Talking to Skyller from inside Daily is a channel, contracted separately.
Two things, two controls
Actions and events
What the vendor offers in Daily.
Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.
Showing 11 of 11
Batch Create Rooms
DAILY_BATCH_CREATE_ROOMS
Create 1 to 1,000 Daily rooms in one atomic request. If any room fails, Daily creates none of the rooms. Paid media, telephony, storage, and callback settings are intentionally not exposed.
Create Meeting Token
DAILY_CREATE_MEETING_TOKEN
Issue a time-bounded meeting token for one Daily room and participant. The returned token grants room access and must be handled as a secret.
Create Room
DAILY_CREATE_ROOM
Create a named Daily room with privacy and optional safe meeting defaults. Paid media, telephony, storage, and callback settings are intentionally not exposed.
Delete Room
DAILY_DELETE_ROOM
Permanently delete one Daily room by name. Use only after confirming the target; active participants may be disconnected.
Get Domain Config
DAILY_GET_DOMAIN_CONFIG
Return the connected Daily domain identity and stable account capability signals. Use this before attempting features that may be disabled or entitlement-gated.
Get Room
DAILY_GET_ROOM
Return a Daily room's current privacy and configuration by room name.
Get Room Presence
DAILY_GET_ROOM_PRESENCE
Return the current participants visible in one Daily room, optionally filtered by user ID or display name.
List Meetings
DAILY_LIST_MEETINGS
Return one page of Daily meeting-session analytics, filtered by room, time range, or session state. Pass next_cursor unchanged to continue.
List Rooms
DAILY_LIST_ROOMS
Return one reverse-chronological page of Daily rooms. Pass next_cursor unchanged to continue with the same filters.
Update Room
DAILY_UPDATE_ROOM
Update a Daily room's privacy or safe meeting defaults. Only supplied fields change; paid media, telephony, storage, and callbacks are not exposed.
Validate Meeting Token
DAILY_VALIDATE_MEETING_TOKEN
Validate a Daily meeting token and return its effective room and participant settings without joining a call.
Before you start
What your company needs to use Daily.
Login
Each person enters their own Daily API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Daily for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
11 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.