Skip to content

Integration · Calendar and scheduling

Cal in Skyller.

Connect Cal to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Actions and events

Cal

Cal simplifies meeting coordination by providing shareable booking pages, calendar syncing, and availability management to streamline the scheduling process

Actions
168
Events
0
Composio catalog
Sign-in or API key
Global — no specific country
re-read from the vendor every 24 hours
cal.com

168 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

SIGN-IN OR API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in Cal and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in Cal.

  1. Input

    A team member asks, in the conversation, for something that today requires opening Cal — inside their area's space, with their login.

  2. What Skyller does

    1. 01Picks, among the enabled functions, a query action and looks the information up in Cal with the person's own credential.
    2. 02If the request requires writing something in Cal, shows the card with what it is about to do and waits for Approve.
    3. 03Returns the result in the conversation and records who asked, which action was used and when.
  3. Result

    Cal stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

  • The available actions are the ones the vendor publishes for Cal; in your company only the functions turned on by the administrator are available.
  • If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
  • Being in this catalog does not mean being installed, with a valid login, working in your company.

Where this helps your work

Cal inside the conversation where the work happens.

Three common situations for people who use Cal every day. What Skyller does in each one depends on the functions your company turns on.

Organizing the agenda

“When do I have a free hour with the customer this week?”

The person asks and Skyller checks their calendar in Cal, with their login, and suggests times.

Calendar read in the conversation

Scheduling

“Book Thursday's 10 am meeting with finance.”

Creating an event is a write action: Skyller shows the card with date, attendees and title and creates it in Cal after Approve.

Meeting created with approval

Administering

“Everyone sees their own calendar.”

The Cal connection uses each person's account; the administrator turns on only the routine's functions and sees the record of every event created.

Own account, a record per event

Actions and events

What the vendor offers in Cal.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

  • Add attendee

    CAL_ADD_ATTENDEE

    Tool to create a new attendee for an existing booking in Cal.com. Use when you need to add an additional participant to a scheduled event.

  • Add member to team

    CAL_ADD_MEMBER_TO_TEAM_USING_ORG_AND_TEAM_ID

    Adds a new member to a specified team within an organization by creating a team membership.

  • Add organization attribute option

    CAL_ADD_ORGANIZATION_ATTRIBUTE_OPTION

    Adds a new option to an organization's SINGLE_SELECT or MULTI_SELECT attribute. Use this action to extend the available choices for an existing attribute.

  • Cancel booking via uid

    CAL_CANCEL_BOOKING_VIA_UID

    Cancels an existing and active Cal.com booking using its unique identifier (UID).

  • Check calendar availability

    CAL_CHECK_CALENDAR_VERSION2

    Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary.

  • Check gcal synchronization status

    CAL_CHECK_GCAL_SYNCHRONIZATION_STATUS

    Call this read-only action to verify the connection and synchronization status of a user's Google Calendar integration with Cal.

  • Check ics feed calendar endpoint

    CAL_CHECK_ICS_FEED_CALENDAR_ENDPOINT

    Checks an ICS feed URL (expected as a query parameter) to verify its validity, accessibility, and iCalendar data integrity.

  • Check Stripe status

    CAL_CHECK_STRIPE_STATUS

    Verifies if Stripe is correctly connected to the Cal scheduling system and functional for processing payments, reporting only on the integration's status.

  • Check team stripe integration status

    CAL_CHECK_TEAM_STRIPE_INTEGRATION_STATUS

    Retrieves the Stripe integration status and related information for a team, primarily to verify account connection, subscription details, or payment setup; this is a read-only operation that does not modify Stripe settin…

  • Confirm booking by uid

    CAL_CONFIRM_BOOKING_BY_UID

    Confirms an existing booking by bookingUid if the booking exists and is in a state allowing confirmation (e.g., not already cancelled or confirmed); this finalizes the booking, does not modify its details, and should typ…

  • Connect to calendar

    CAL_CONNECT_TO_CALENDAR

    Initiates or checks the external connection status for a specified calendar, possibly returning a redirect URL for user authorization to complete integration, without altering calendar data.

  • Create membership for organization

    CAL_CREATE_MEMBERSHIP_FOR_ORGANIZATION

    Creates a new membership for a user within a Cal.com organization. The caller must have admin/owner access to the organization, and the target user must already exist in the system.

Before you start

What your company needs to use Cal.

Login
Sign-in to the Cal account or an API key, depending on what your account in the service allows. Either way the credential belongs to the person and is encrypted.
Who installs
An administrator connects Cal for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
168 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide

Common doubts before connecting Cal.

Next step

Connect Cal and try it with your team.

Try it free with your team or book a demo: together we pick the Cal functions to enable and show the first approved action, with fictitious data.