CalendarLink
SchedulingConnect AI agents to CalendarLink, a platform for add-to-calendar links, RSVPs, and subscription calendars. Agents create events, list registrations, manage collections, and look up contacts so event promotion and RSVP tracking run without manual upkeep.
What This Integration Enables
CalendarLink is not a booking tool, and reading it as one leads you to the wrong workflows. Nothing here reserves capacity or negotiates a time. The unit of work is a shareable URL: an add-to-calendar link for a single event, a public collection that behaves as a subscribable calendar, and the RSVP responses that come back from both. Agents read the organization through Get Current User, list upcoming and past events, retrieve an event with its add-to-calendar url, and publish new ones into a collection with a timezone, a location, and optional RSVP with a deadline. On the audience side they read registrations per event and pull contact records with their activity counts.
The shape of the operations tells you what this platform is for. There is a Create Event and a Create Collection, and an Update Collection for the container, but this connector exposes no operation to edit or remove an event once it exists. That is the defining fact about working with CalendarLink through an agent, and the workflows below are built around it rather than in spite of it. Descriptions and locations are capped at 255 characters and location URLs at 500, so an agent composing copy needs to fit the format rather than discover the limit at publish time. Every action is built and verified against the CalendarLink API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Announcement With a Working Calendar Link
A webinar date is confirmed. The agent creates the event in the right collection with Create Event, capturing the timezone explicitly so attendees in other regions get the correct local time, and enables RSVP with a deadline. It takes the returned add-to-calendar url and passes it into the announcement sequence in Mailchimp and the reminder that goes out through Gmail. One link, generated from the source record, used everywhere. Nobody rebuilds it per channel and nobody ships an email with last quarter's link in it.
RSVP Reconciliation Into the CRM
The morning after an announcement goes out, the agent runs List Event Registrations for the event and walks the pages. For each responder it runs Get Contact to pull the full record with activity counts, then upserts the person into HubSpot with the event attached, flagging anyone whose registration count across events crosses the threshold the team treats as real intent. The sales team sees who keeps showing up rather than a raw export. The agent also writes a per-event summary to Google Sheets so attendance trends are visible across the season.
A Subscription Calendar for a Whole Season
A conference program runs across three months. Rather than sending a link per session, the agent runs Create Collection once with the appropriate appearance from List Appearances, sharing enabled and registration configured, then publishes each confirmed session into it with Create Event as the program firms up. Attendees subscribe to the collection's public url a single time and every later session appears in their own calendar automatically. The agent keeps the internal program in Notion aligned with what has actually been published, using List Events and List Past Events as the source of truth for what is live.
Human-in-Loop Highlight
Publishing is the irreversible act here, and the connector says so by omission. Create Event returns an add-to-calendar url that people immediately save into their own calendars, and this connector exposes no operation to edit or delete that event afterward. A wrong start time, a stale meeting link inside the location field, or a typo in the title is not something an agent can quietly correct on the next run. Update Collection has the same shape at a larger scale: it rewrites a calendar that List Collections reports as having active subscribers, and those subscribers see the changed container in their own calendar app without being told. So the agent composes the event, resolves the timezone, checks List Events for a near duplicate, reads the subscriber count on the target collection, and then stops. It sends the marketing owner the rendered detail in Slack: "Ready to publish [title] on [date] at [time] [timezone] into [collection], which has [n] active subscribers. This link cannot be edited or withdrawn from here. Publish, change the details, or hold?" The owner answers. Reads, RSVP pulls, and contact syncs run untouched. The one call whose output lands in strangers' calendars gets a person's name on it.
Agent Capabilities
12 actionsAccount
1- Get Current User Returns the authenticated user with their id, email, name, and the organizations they belong to. Use it to discover the organization id every other operation requires.
Events
5- List Events Returns a paginated list of upcoming events, each with its id, add-to-calendar url, title, start and end times, timezone, state, and RSVP settings. The duplicate check before publishing.
- List Past Events Returns a paginated list of past events ordered by start time. Used for post-season reporting and for confirming what was actually published.
- Get Event Returns the full detail of a single event, including its add-to-calendar url, recurrence, times, timezone, state, description, location, and RSVP configuration.
- Create Event Creates an event inside a collection and returns a shareable add-to-calendar url. Requires a collection, a title, and a start time. Descriptions and locations are limited to 255 characters and the location URL to 500. Routed for human approval, because this connector exposes no operation to edit or remove the event afterward.
- List Event Registrations Returns a paginated list of RSVP registrations for an event. The read that tells you who actually responded, per event, without an export.
Collections
4- List Collections Returns the organization's event collections with their sharing and registration settings, public url, and counts of events and active subscribers. Read the subscriber count before proposing any change to a collection.
- Create Collection Creates a collection, which groups events under a shareable public calendar and controls how it looks and behaves. Requires a name and an appearance, with optional toggles for showing event details, single or all event adds, sharing, and required registration.
- Update Collection Updates an existing collection's name, appearance, description, and behavior toggles. Changes propagate to a calendar people have already subscribed to, so this is routed for confirmation.
- List Appearances Lists the appearance themes available to the organization. The appearance id is what Create Collection and Update Collection use to control the visual style of a shared calendar.
Contacts
2- List Contacts Returns a paginated list of contacts, the people who have interacted with the organization's events, each with an id, name, and email.
- Get Contact Returns full detail for a single contact, including phone, country, notes, and activity counts across events, registrations, subscriptions, and activities. Used to separate a repeat attendee from a one time responder.
Frequently Asked Questions
What can FlowRunner do with CalendarLink?
FlowRunner agents can run Get Current User, List Appearances, and List Events in CalendarLink, plus 9 more actions.
Does connecting CalendarLink to FlowRunner require OAuth?
No. CalendarLink connects to FlowRunner with an API key, no OAuth flow required.
Can CalendarLink trigger a FlowRunner workflow automatically?
CalendarLink doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with CalendarLink
$100 in credits. No card required. Connect in minutes.