Scheduling · Integration

AI agents for Calendly

Bookings that should kick off preparation automatically. AGNT connects to Calendly so agents can read what happens there, reason about it, and act — with a receipt for every run.

Download AGNT free Browse the marketplace

Calendly and AGNT, in brief

What it does	Lets an AGNT agent read from and act in Calendly.
Connects with	An API key held in the local vault
AGNT node	calendly-api, receive-calendly-booking
Runs when	A meeting is booked
Typical build time	Two minutes
Where data goes	Nowhere by default — AGNT runs on your machine and credentials never leave it.

What you can automate

Reacts when…

a meeting is booked
a booking is cancelled

Agents can…

read booking details
trigger prep workflows

Teams use it for

research briefs before every booked call
no-show follow-ups sent automatically
bookings logged into the CRM

Copy this Calendly workflow

A concrete shape to start from: the workflow wakes when a meeting is booked in Calendly. The agent gathers the surrounding context, forms a view, and where it is warranted goes on to read booking details — or to trigger prep workflows. Nothing is copied blindly, and choosing to take no action is a legitimate outcome recorded in the receipt.

Three nodes carry that: something happens in Calendly, an agent reads it and forms a view, and it acts only where that view says it should. The definition below is the whole thing — paste it into a new workflow and it loads exactly as drawn.

The whole flow runs locally against your own Calendly account. Deciding to take no action counts as an outcome and is recorded like any other.

Calendly — read, decide, actpaste into a new workflow

{
  "id": "c1812317-6de5-4a5c-ab05-2b19eb65505c",
  "name": "Calendly — read, decide, act",
  "nodes": [
    {
      "id": "fa48a3c2-7ddb-4235-ad89-e6c534b443fa",
      "text": "Watch Calendly for activity",
      "x": 512,
      "y": 144,
      "isEditing": false,
      "type": "receive-calendly-booking",
      "icon": "clock",
      "category": "trigger",
      "isSelected": false,
      "parameters": {},
      "description": "Poll Calendly for newly-created upcoming scheduled events and trigger the workflow when a new booking is detected.",
      "error": null,
      "isActive": false,
      "output": null,
      "outputs": {}
    },
    {
      "id": "82613cc6-af23-4cf2-a4bf-e2dab31bbea4",
      "text": "Read it and decide",
      "x": 512,
      "y": 336,
      "isEditing": false,
      "type": "agnt-agent",
      "icon": "agnt",
      "category": "action",
      "isSelected": false,
      "parameters": {
        "instructions": "Read the Calendly item and decide whether it warrants action. Explain your reasoning."
      },
      "description": "Judges the Calendly item against criteria you wrote in plain language.",
      "error": null,
      "isActive": false,
      "output": null,
      "outputs": {}
    },
    {
      "id": "23c78524-f603-4bfa-a9f3-93f6e6ff0d4c",
      "text": "Act in Calendly",
      "x": 512,
      "y": 528,
      "isEditing": false,
      "type": "calendly-api",
      "icon": "connect",
      "category": "action",
      "isSelected": false,
      "parameters": {
        "action": "GET_CURRENT_USER"
      },
      "description": "Runs GET_CURRENT_USER on your behalf.",
      "error": null,
      "isActive": false,
      "output": null,
      "outputs": {}
    }
  ],
  "edges": [
    {
      "id": "a7ae3806-24c4-42c5-a80b-39a301e5cfee",
      "start": {
        "id": "fa48a3c2-7ddb-4235-ad89-e6c534b443fa",
        "type": "output"
      },
      "end": {
        "id": "82613cc6-af23-4cf2-a4bf-e2dab31bbea4",
        "type": "input"
      },
      "startX": 800,
      "startY": 168,
      "endX": 512,
      "endY": 360
    },
    {
      "id": "19dbd8d6-9277-4415-a6bc-fb1159f6257e",
      "start": {
        "id": "82613cc6-af23-4cf2-a4bf-e2dab31bbea4",
        "type": "output"
      },
      "end": {
        "id": "23c78524-f603-4bfa-a9f3-93f6e6ff0d4c",
        "type": "input"
      },
      "startX": 800,
      "startY": 360,
      "endX": 512,
      "endY": 552
    }
  ],
  "zoomLevel": 1,
  "canvasOffsetX": 0,
  "canvasOffsetY": 0,
  "isTinyNodeMode": false
}

Run this against your own Calendly

AGNT Community Core is free and runs on your own machine. Nothing about this workflow leaves it.

Download AGNT free Browse the marketplace

A booking is a trigger to prepare

The moment a meeting is booked is the ideal time to start research, and the least likely time for anyone to do it. An agent can produce the briefing — who they are, what they do, what they asked for — well before the call appears on anyone’s horizon.

The other end of the funnel

Cancellations and no-shows are equally automatable: follow-ups sent, the CRM updated, and the slot flagged, without anyone remembering to check.

Inside the Calendly API node

Use Calendly with AGNT workflows via a Calendly Personal Access Token stored as the calendly auth provider.

What it can do: GET_CURRENT_USER LIST_EVENT_TYPES GET_AVAILABLE_TIMES CREATE_SCHEDULING_LINK BOOK_INVITEE LIST_SCHEDULED_EVENTS CANCEL_EVENT

Full Calendly API parameter reference

Parameter	Type	What it does
`action`required	string	The Calendly operation to perform. GET_CURRENT_USER · LIST_EVENT_TYPES · GET_AVAILABLE_TIMES · CREATE_SCHEDULING_LINK · BOOK_INVITEE · LIST_SCHEDULED_EVENTS · CANCEL_EVENT
`userUri`required	string	Calendly user URI. Required for some list operations unless organizationUri is provided. Example: https://api.calendly.com/users/USER_UUID
`organizationUri`required	string	Calendly organization URI. Example: https://api.calendly.com/organizations/ORG_UUID
`eventTypeUri`required	string	Calendly event type URI or UUID. Required for availability, scheduling links, and booking.
`scheduledEventUri`required	string	Calendly scheduled event URI or UUID. Required for cancellation.
`startTime`required	string	ISO 8601 start time. For availability/listing, use the start of the search window. For booking, use the selected meeting start time in UTC ending with Z.
`endTime`required	string	ISO 8601 end time for availability or event listing windows. Calendly available-times supports a maximum 7-day window per request.
`timezone`required	string	Timezone for invitee or display, e.g. America/New_York or UTC.
`inviteeName`required	string	Invitee full name. Required for BOOK_INVITEE.
`inviteeEmail`required	string	Invitee email address. Required for BOOK_INVITEE.
`eventGuests`required	string	Optional comma-separated guest email list, or JSON array of guest emails.
`questionsAndAnswersJson`required	string	Optional JSON array for Calendly invitee questions and answers.

10 further parameters are available on the node itself.

Every parameter above is read from the shipped calendly-api node, so it cannot drift from the product.

Connect Calendly in two minutes

Download AGNT Community Core — free, local-first, no account needed to run.
Connect by pasting an API key into AGNT’s vault — stored encrypted on your machine, never uploaded.
Drop the Calendly node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.