← Back to Skills Marketplace
byungkyu

Calendly

by byungkyu · GitHub ↗ · v1.2.7 · MIT-0
cross-platform ✓ Security Clean
19388
Downloads
14
Stars
0
Active Installs
14
Versions
Install in OpenClaw
/install calendly-api
Description
Calendly API integration with managed OAuth. Access event types, scheduled events, invitees, availability, and manage webhooks. Use this skill when users want to view scheduling data, check availability, book meetings, or integrate with Calendly workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Calendly connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Calendly action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Calendly examples; they add no Calendly capability - Calendly is itself an event source, so its own events are in `references/calendly/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to connect Calendly through Maton. Before approving writes, webhooks, trigger destinations, or hosted functions, check the exact account, destination URL, data fields, and persistence, especially because invitee details and meeting links may be forwarded automatically if you approve automation.
Capability Assessment
ℹ Credentials
Network access, OAuth, and optional raw API-key HTTP fallback are proportionate for an API integration, with clear guidance to prefer managed CLI credentials and avoid exposing tokens.
ℹ Install Mechanism
Installation uses a pinned Maton CLI version via npm or Homebrew and requires network access and a Maton account; no automatic install-time execution beyond normal package installation is documented.
✓ Instruction Scope
Instructions default to read/list calls, require explicit approval for OAuth connections, writes, deletes, hosted functions, trigger destinations, and webhooks, and warn that third-party API content must be treated as untrusted data.
ℹ Persistence & Privilege
OAuth sessions, connections, hosted functions, triggers, destinations, and Calendly webhooks can persist, but the artifact clearly discloses persistence, requires user approval, and provides deletion/cleanup guidance.
✓ Purpose & Capability
The skill’s stated purpose is Calendly API access through Maton OAuth, including event types, scheduled events, invitees, availability, webhooks, functions, and triggers; those capabilities match the documented purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install calendly-api
  3. After installation, invoke the skill by name or use /calendly-api
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.7
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.6
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.5
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.4
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.3
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.2
Fix the raw HTTP fallback example: restore the gateway base URL in the GATEWAY constant (and the fastmail streaming call), which a previous edit had replaced with a placeholder
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.4
- Updated API base URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai throughout documentation and examples. - Expanded security and permissions section; clarified the requirement for explicit user approval for all write operations. - Adjusted connection management instructions, consolidating endpoints under api.maton.ai. - Minor clarifications on using the Maton-Connection header when working with multiple accounts. - Removed the LICENSE.txt file.
v1.0.3
- Metadata updated to include required environment variables under a new "clawdbot" section. - No functional or documentation changes to user-facing features.
v1.0.2
- Documentation formatting and clarity improved in SKILL.md. - No functional or code changes; only SKILL.md was updated.
v1.0.1
- Added a note in the description about using the api-gateway skill for other third party apps. - Changed all example commands from cURL to Python (using the standard library) for authentication, connection management, and API calls. - Updated authentication header examples to reference the $MATON_API_KEY environment variable format. - All block examples for listing, creating, getting, and deleting connections, as well as API reference usage, now use Python instead of cURL.
v1.0.0
Major update: Migrated Calendly skill to managed OAuth via Maton platform and expanded documentation. - Migrated from manual API key management to OAuth connections via Maton control panel. - Updated API endpoints to use the Maton gateway and OAuth flow. - Added clear instructions for obtaining, managing, and using the Maton API key and OAuth Calendly connections. - Expanded documentation to cover authentication, connection management, base URLs, and header usage. - Simplified example usage, with ready-to-use curl command examples for each endpoint. - Removed the old CLI-oriented README and replaced with Maton-focused API reference and usage guides.
Metadata
Slug calendly-api
Version 1.2.7
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 14
Frequently Asked Questions

What is Calendly?

Calendly API integration with managed OAuth. Access event types, scheduled events, invitees, availability, and manage webhooks. Use this skill when users want to view scheduling data, check availability, book meetings, or integrate with Calendly workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Calendly connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Calendly action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Calendly examples; they add no Calendly capability - Calendly is itself an event source, so its own events are in `references/calendly/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 19388 downloads so far.

How do I install Calendly?

Run "/install calendly-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Calendly free?

Yes, Calendly is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Calendly support?

Calendly is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Calendly?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.7.

💬 Comments