Cal.com, without opening Cal.com.
Read-only bookings and availability, the open-source scheduling stack.
In your channel
Ask Ray for something in Cal.com and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Cal.com
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Cal.com
- Fetch all bookings
- Retrieve booking details by uid
- Get team bookings
- List attendees
- List event types
- Retrieve event type by id
- Get available slots info
- Retrieve calendar busy times
- Retrieve schedules list
- Get default schedule details
- Retrieve my information
- Get teams list
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Add someone to a Cal.com booking
- Cancel a Cal.com booking
- Confirm a Cal.com booking
- Decline a Cal.com booking
- Correct a Cal.com attendee
- Edit a Cal.com booking
- Mark a Cal.com no-show
- Book a Cal.com meeting
- Reassign a Cal.com booking
- Reassign a Cal.com booking to the next available host
- Reschedule a Cal.com booking
- Hold a Cal.com slot
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete all team event type webhooks
- Disconnect calendar using credential id
- Delete conference app connection
- Fetch provider access token
- Delete destination calendar by id
How Ray works with Cal.com
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Cal.com
One click, right where you asked. Ray posts a connect card, you authorise Cal.com with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Cal.com, and tell Dana it is being looked at.
Add someone to a Cal.com booking
- Waiting on
- your approval
What does connecting Cal.com to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Cal.com and it can do the Cal.com part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Cal.com account, so Ray can only reach what that person can already reach, and the history in Cal.com shows who actually asked.
Security and permissions
- You authorise Cal.com on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Cal.com in a message, or uninstall Ray and every connection it held is revoked.
More calendars & scheduling integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Cal.com.
Free to start, no credit card, and it asks before it acts.