Marketplace / scheduling-calendly

Scheduling — Calendly

Scrape Calendly pages and intersect their slots with my calendar.

by Agentum 1 installs v1.0.4 integrations
Open in Agentum
Requires the Agentum app

Scheduling — Calendly

What it does

This is an add-on for the Scheduling agent. When an inbound email contains a Calendly booking link (anything under calendly.com), this capability quietly fetches the open time slots from that page and hands them to the scheduling agent. The scheduling agent then compares those slots against your own calendar and proposes the times that work for both of you.

You don’t trigger this capability directly — it just runs whenever a Calendly link shows up in a scheduling thread. There is no UI panel to open and no commands to run.

There is also no account to connect. Calendly’s public booking pages are anonymous, so this capability reads them the same way a browser would, with no API key or sign-in required.

Settings

Both settings live in the capability’s settings tab.

  • Look-ahead window (days) — How far ahead to look at Calendly availability when the booking link doesn’t itself pin a date range. Default is 14 (two weeks). Increase if you typically schedule further out; large values will be slower and may bump into Calendly rate limits.
  • Timezone — The IANA timezone used for both the availability query and how slots are described back to you. Default is UTC, which is usually wrong — set this to your local zone, for example America/Los_Angeles, Europe/London, or Asia/Tokyo.

Integrations

  • Calendly (calendly.com) — Outbound reads of public booking pages only. No login, no API key, no Calendly account required on your end.

The capability also needs the Scheduling agent installed and enabled. Without it, this add-on has nothing to plug into.

Known limits

  • Public pages only. If a Calendly page is private, SSO-gated, or has been disabled by its owner, no slots will come back. The scheduling agent will then fall back to its normal counter- proposal flow.
  • No caching. Each inbound email re-fetches the page. If you receive many emails referencing the same link in quick succession, expect a small delay per fetch.
  • Meeting duration is inferred from the URL slug. A link ending in /30min is treated as 30 minutes, /15min as 15, and so on. Links without a duration hint default to 30 minutes.
  • Shortened links aren’t matched. Only direct calendly.com URLs are detected. Links wrapped through trackers or URL shorteners are skipped until they resolve to the real URL.
  • Calendly’s endpoints are undocumented. They have been stable in practice, but Calendly may change them without notice. If fetches start returning no slots after a Calendly update, the capability needs a patch.