Integration · Projects and tasks
AI agents for Cronofy
Read a person's events and free/busy time across every calendar they linked through Cronofy.
- Actions
- 7
- Read
- 4
- Write
- 3
Actions
What your agents can do in Cronofy
Read a person's events and free/busy time across every calendar they linked through Cronofy (Google, Microsoft 365, Exchange, iCloud, Outlook.com), and create, update or delete events and answer invitations, in the Cronofy data center where the account lives.
Read 4
Look things up. Nothing changes.
Get the account and its calendars
Reads the connected Cronofy account: its sub (account ID), email, name and default time zone (zoneinfo), and under cronofy.data.profiles each linked calendar service with its calendars.
Read events
Lists events across the person's calendars between two dates (Cronofy keeps 42 days back and 201 days ahead).
Read the next page of events
Fetches a further page of a Read events result.
Get free/busy time
Lists the person's busy blocks between two dates without event details: each with calendar_id, start, end and free_busy_status (busy, tentative, free or unknown).
Write 3
Create, change or send.
Create or update an event
Creates an event in one of the person's calendars, or updates it when an event with the same event_id was created before in that calendar.
Delete an eventDeletes data
Deletes an event this tool created, by its calendar_id and your event_id (the key given when it was created).
Answer an invitation
Accepts, tentatively accepts or declines an invitation in the person's calendar, by the event's calendar_id and event_uid from Read events.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Sign in with Cronofy and approve access (OAuth).
Settings
- Data center
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Cronofy data
Ask a question in plain words. The agent can get the account and its calendars, read events or read the next page of events in Cronofy, then answers with what it found.
- 02
Let an agent update Cronofy
Have the agent create or update an event or delete an event in Cronofy as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Cronofy and Slack: it can get the account and its calendars in Cronofy and post a summary to a Slack channel in the same run.
FAQ
Cronofy and MyDeepAgents
Can MyDeepAgents connect to Cronofy?
Yes. The Cronofy connector has 7 actions: 4 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Cronofy?
Sign in with Cronofy and approve access (OAuth). The connection also asks for: Data center. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Cronofy without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Cronofy in workflows as well as agents?
Yes. Every Cronofy action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Cronofy to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.