Cal Integration & Booking Workflow Automation
Run Cal on autopilot. Keep the veto.
175 actions
Booking changes, cancellations, and schedule updates fire inside Cal before you've had a chance to review them. Rills proposes each action and waits for your call.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential productivity action from Cal arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Reschedule 3 conflicting bookings to next available slots?
3 bookings flagged · host unavailable on original date
Same attendees rebooked successfully last month
No client replies received in past 24h
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Cal automation
Scheduling changes feel low-stakes until one fires at the wrong time: a booking gets cancelled for the wrong person, a team event type goes live before the details are final, or a private link updates while a client is mid-flow.
When Cal runs unsupervised
Most Cal operations look routine until they aren't. A reschedule or cancellation that hits the wrong uid can unravel a week of coordination before you see a single reply.
- Rescheduling a booking by uid without review reassigns a client meeting to a slot they never agreed to.
- Cancelling a booking via uid on a recurring call removes every future instance, not just the one you meant.
- Creating a team event type pushes a new booking page live before the copy, duration, or availability is confirmed.
- Updating a user schedule in the organization changes what slots show to all external bookers immediately.
- Updating a private link mid-campaign breaks any link a prospect has already saved or shared.
What Rills does inside Cal
With Rills handling Cal automation, operations like reschedule booking by uid, cancel booking via uid, and create team event type get queued as proposals. Nothing posts to a calendar or goes out to a booker until you've seen it.
The booking still gets rescheduled; you just approve it before it reaches the client.
Why Cal has no triggers and how Rills fills the gap
Cal does not emit triggers on its own, so Rills uses scheduled polling and upstream signals to decide when to act. You can approve Cal changes on a cadence that fits your workflow without waiting for an event to fire.
- Scheduled reschedule sweep: poll pending bookings on a set interval, surface any uid flagged for rescheduling, and queue for approval before the calendar updates.
- Team event type audit: run a recurring check against get event type by team id to catch any event type that has drifted from your approved template.
- Org membership review: pull retrieve team memberships on a schedule to surface additions or removals before they affect who can book or manage availability.
- Private link rotation: trigger update private link as part of a campaign-end workflow sourced from your CRM or email tool, so the old link stops working only after you approve the swap.
What Rills can do in Cal
3 of 175 actions across reads, writes, and updates.
- 01
Cancel booking via uid
Remove an existing booking from your calendar by its unique identifier, allowing you to free up time and notify attendees automatically. This is useful when appointments need to be cancelled due to scheduling conflicts, client cancellations, or no-shows.
- 02
Connect to calendar
Establishes a connection between your application and a calendar service, providing authorization details needed to access and manage calendar data. This enables your tools to read and interact with your calendar events without manual syncing.
- 03
Create team event type
Set up a new scheduling template for your team that defines how clients can book meetings with specific team members or groups. This lets you standardize booking details like duration, buffer time, and which calendar the event syncs to.