Calendar and meetings
Calendly
Upcoming and recent bookings for a client's event type, counts and times only.
Free for 14 days. No credit card needed.
What it does
Connect Calendly to your client work.
- Bookings at a glance
Upcoming bookings for the next 60 days, meetings held in the last 30, and the next five times.
A tile on the client's Overview - No invitee details
Only counts and times are read: no names or emails.
Everywhere
How it works
Connect once. It keeps itself current.
- 1Connect with a personal access token
It reads the bookings of the Calendly user who creates it.
- 2Pick an event type per client
Or all event types; it syncs right away.
- 3About once a day
Matches sync again on the scheduled run once the last sync is a day old, or with Sync now.
What Brava can change
Changes in Calendly, only when you press Apply.
Ask Brava for a change and it reads Calendly live, then shows it on a card: what changes, before and after, and the limits it was checked against. Nothing is written until someone on your team presses Apply. The proposal and the change are both logged on the client's record.
- Create a single-use booking linkNo undo
Creates a single-use booking link for the client's matched event type, to send to the client.
- Single-use: the link works for one booking.
No undo: an unused link simply goes unused.
A proposal can be applied for 15 minutes; where there is an undo, it is offered for 7 days. No change deletes anything that was there before.
Before you start
What you need.
- A Calendly account (the user whose bookings count).
- A personal access token from Integrations, API & Webhooks.
Setting it up
Where to find it.
- Log in to Calendly.
- Open Integrations, then API & Webhooks.
- Generate a personal access token and copy it.
In the app, Connect Calendly opens a guided setup with Brava: it asks for each thing in turn, tests the connection and tells you it is working.
Data and privacy
What BravaSpace keeps, and what it can touch.
What is stored
The Calendly credentials, encrypted (AES-GCM) in a table no browser can read, plus the last four characters to tell keys apart, and the synced numbers per client for 60 days.
Access
Reads scheduled events, counted; no invitee is read, and these numbers are not shared with the AI. The token can also write: Ask Brava can propose a single-use booking link for the client's event type, created in Calendly only when you press Apply on its card. Nothing else is changed.
Disconnecting
Disconnect Calendly on its page: the credentials, every client match and all synced Calendly numbers are deleted. Nothing changes in your Calendly account.
Questions
Calendly questions.
Bookings at a glance; no invitee details. Reads scheduled events, counted; no invitee is read, and these numbers are not shared with the AI. The token can also write: Ask Brava can propose a single-use booking link for the client's event type, created in Calendly only when you press Apply on its card. Nothing else is changed.
Open Connect Calendly in BravaSpace and paste the personal access token; Brava tests the connection before saving it. Log in to Calendly. Open Integrations, then API & Webhooks. Generate a personal access token and copy it. Then match each client to their Calendly event type.
The Calendly credentials, encrypted (AES-GCM) in a table no browser can read, plus the last four characters to tell keys apart, and the synced numbers per client for 60 days.
Disconnect Calendly on the Calendly app page in BravaSpace: the credentials, every client match and all synced Calendly numbers are deleted. Nothing changes in your Calendly account.
Brava reads the error and suggests the fix. The common ones: Calendly did not accept the token. Generate a new one under Integrations, API & Webhooks.
Try it with one client.
Add some work. Share a file. Ask for feedback. See what your client sees, with your name on it. Free for 14 days. No credit card needed.