First-party app

Calendly

Name: Calendly
Author: w6w

Read Calendly users, event types, scheduled events and invitees; create single-use scheduling links and manage webhook subscriptions.

stable Calendar & SchedulingProductivity

About

Calendly ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.

App id: io.w6w.calendly
Version: 0.1.2
Author: w6w
Licence: MIT
Categories: Calendar & Scheduling · Productivity

Overview

Calendly manages who’s meeting whom and when. This app reads users, event types, scheduled events and their invitees, generates single-use scheduling links a workflow can hand out, and manages webhook subscriptions so Calendly can notify a workflow when something books or cancels.

Every object is addressed by Calendly’s own absolute identifier, and actions that take a single object accept either that identifier or the bare id, so results from one call feed directly into the next without extra parsing. Reading the current user or looking up a specific scheduled event and its invitees covers the common case of finding out who booked what and when, without opening the Calendly dashboard.

A good fit for workflows built around booking events — creating a one-off scheduling link for a specific request, reacting to a new booking through a webhook, or pulling invitee details into a CRM or support ticket the moment someone schedules time.

Build with Calendly

Three routes to the same 12 actions. The Workflow tab is generated from Calendly's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Actions Workflow Code MCP

Get Event Type

event-type-get

Fetch a single event type by URI or UUID.

List Event Types

event-type-get-many

List event types for a user or organization (GET /event_types). Supply one of `user` or `organization`.

Get Event Invitee

invitee-get

Fetch a single invitee of a scheduled event (GET /scheduled_events/{uuid}/invitees/{uuid}).

List Event Invitees

invitee-get-many

List invitees for a scheduled event (GET /scheduled_events/{uuid}/invitees).

Get Scheduled Event

scheduled-event-get

Fetch a single scheduled event by URI or UUID.

List Scheduled Events

scheduled-event-get-many

List booked meetings for a user or organization (GET /scheduled_events). Supply one of `user` or `organization`.

Create Scheduling Link

scheduling-link-create

Create a single-use scheduling link for an event type (POST /scheduling_links).

Get User

user-get

Fetch a Calendly user by URI or UUID.

Get Current User

user-get-current

Fetch the user associated with this connection (GET /users/me).

Create Webhook Subscription

webhook-subscription-create

Subscribe a URL to Calendly events (POST /webhook_subscriptions).

Delete Webhook Subscription

webhook-subscription-delete

Delete a webhook subscription by URI or UUID (DELETE /webhook_subscriptions/{uuid}).

List Webhook Subscriptions

webhook-subscription-get-many

List registered webhooks for a scope (GET /webhook_subscriptions).

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Calendly's real ids.

{
  "manifestVersion": "2",
  "name": "calendly-example",
  "steps": [
    {
      "id": "event-type-get",
      "uses": {
        "app": "io.w6w.calendly",
        "action": "event-type-get",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "eventType": "<eventType>"
      }
    }
  ]
}

Here are some of the things you can do

Get Event Type
read
event-type-get
List Event Types
read
event-type-get-many
Get Event Invitee
read
invitee-get
List Event Invitees
read
invitee-get-many
Get Scheduled Event
read
scheduled-event-get

+7 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Calendly, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Calendly. The Workflow tab is where this app's real ids are.

JS SDK CLI

Install

npm yarn pnpm deno

npm install @w6w/sdk

yarn add @w6w/sdk

pnpm add @w6w/sdk

deno add npm:@w6w/sdk

Code

import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "scheduling-link-create",
  payload: {
    owner: "<value>",
    // maxEventCount: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);

Install the CLI

npm install -g @w6w/cli

CLI

w6w run conn_YOUR_CONNECTION_ID --action scheduling-link-create --payload '{"owner":"<value>"}'

Give an AI agent Calendly — without giving it Calendly's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call

{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.calendly#event-type-get",
    "input": {
      "eventType": "<eventType>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Calendly connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

Calendly's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. Calendly itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Calendly declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Calendly platform status

Atlassian Statuspage rollup for www.calendlystatus.com, with per-component detail. Unauthenticated and unsigned.

quota