← Back to Skills
General

Calendly

Hithesh Jayawardana By Hithesh Jayawardana 👁 7 views ▲ 0 votes

Work with Calendly from chat — view events, check invitees, inspect availability schedules, manage webhooks, and create scheduling links when supported. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Calendly API access yourself. Quick start Install the verified ClawLink plugin: openclaw plugins install clawhub:clawlink-plugin Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet If ClawLink is not configured, call clawlink_begin_pairing Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device After the user confirms approval, call clawlink_get_pairing_status Tell the user to connect Calendly at claw-link.dev/dashboard?add=calendly When the user confirms Calendly is connected, call clawlink_list_integrations and then clawlink_list_tools with the calendly integration slug Setup details Installing the plugin If the ClawLink plugin is not installed yet, tell the user to run: openclaw plugins install clawhub:clawlink-plugin If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog. Pairing ClawLink If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet. Call clawlink_begin_pairing. Tell the user to open the returned pairing URL in their browser. The user signs in to ClawLink if needed and approves the OpenClaw device. After the user confirms approval, call clawlink_get_pairing_status to finish local setup. The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to claw-link.dev. The user should not paste raw credentials into chat. Connecting Calendly Tell the user to open https://claw-link.dev/dashboard?add=calendly and connect Calendly there. The page opens the add-connection panel filtered to Calendly. ClawLink's hosted page runs the Calendly connection flow — the user clicks through Calendly sign-in and consent. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration calendly. Using Calendly tools ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance. Discovery Call clawlink_list_integrations to confirm Calendly is connected. Call clawlink_list_tools with integration calendly. Treat the returned list as the source of truth. Do not guess or assume what tools exist. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration calendly. If no Calendly tools appear, direct the user to https://claw-link.dev/dashboard?add=calendly. Execution Call clawlink_describe_tool before using an unfamiliar tool, before any write, or when the request is ambiguous. Use the returned schema, whenToUse, askBefore, safeDefaults, examples, and followups. Prefer read, list, search, and inspection operations before writes. For scheduling links, no-show changes, webhook changes, or anything marked as requiring confirmation, call clawlink_preview_tool first, then confirm with the user. Execute with clawlink_call_tool. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion. What you can do Typical Calendly tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): View event details List invitees for an event Show upcoming or recent events Check availability schedules List webhook subscriptions Create scheduling links when supported Mark invitees as no-shows when requested Rules Always use ClawLink tools for Calendly. Do not ask the user for separate Calendly credentials. Do not claim a capability is missing without checking the live ClawLink catalog in the current turn. Do not invent slash commands or ask the user to paste raw credentials. Ask for confirmation before writes such as creating links, marking no-shows, or changing webhooks. If Calendly is not connected, direct the user to https://claw-link.dev/dashboard?add=calendly. Never echo or repeat the user's ClawLink credential. Resources ClawLink: https://claw-link.dev ClawLink Docs: https://docs.claw-link.dev/openclaw ClawLink Verification: https://claw-link.dev/verify ClawLink Source: https://github.com/hith3sh/clawlink Calendly API: https://developer.calendly.com/

GitHub
---
name: calendly-scheduling
description: Inspect Calendly events, invitees, availability schedules, and webhook subscriptions, and perform scheduling actions — powered by ClawLink.
---

# Calendly via ClawLink

Work with Calendly from chat — view events, check invitees, inspect availability schedules, manage webhooks, and create scheduling links when supported.

Powered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Calendly API access yourself.

## Quick start

1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet
3. If ClawLink is not configured, call `clawlink_begin_pairing`
4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device
5. After the user confirms approval, call `clawlink_get_pairing_status`
6. Tell the user to connect Calendly at [claw-link.dev/dashboard?add=calendly](https://claw-link.dev/dashboard?add=calendly)
7. When the user confirms Calendly is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `calendly` integration slug

## Setup details

### Installing the plugin

If the ClawLink plugin is not installed yet, tell the user to run:

```
openclaw plugins install clawhub:clawlink-plugin
```

If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.

### Pairing ClawLink

If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.

1. Call `clawlink_begin_pairing`.
2. Tell the user to open the returned pairing URL in their browser.
3. The user signs in to ClawLink if needed and approves the OpenClaw device.
4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.

The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.

### Connecting Calendly

Tell the user to open https://claw-link.dev/dashboard?add=calendly and connect Calendly there. The page opens the add-connection panel filtered to Calendly. ClawLink's hosted page runs the Calendly connection flow — the user clicks through Calendly sign-in and consent. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `calendly`.

## Using Calendly tools

ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.

### Discovery

1. Call `clawlink_list_integrations` to confirm Calendly is connected.
2. Call `clawlink_list_tools` with integration `calendly`.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `calendly`.
5. If no Calendly tools appear, direct the user to https://claw-link.dev/dashboard?add=calendly.

### Execution

1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.
2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.
3. Prefer read, list, search, and inspection operations before writes.
4. For scheduling links, no-show changes, webhook changes, or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.
5. Execute with `clawlink_call_tool`.
6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

## What you can do

Typical Calendly tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):

- View event details
- List invitees for an event
- Show upcoming or recent events
- Check availability schedules
- List webhook subscriptions
- Create scheduling links when supported
- Mark invitees as no-shows when requested

## Rules

- Always use ClawLink tools for Calendly. Do not ask the user for separate Calendly credentials.
- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.
- Do not invent slash commands or ask the user to paste raw credentials.
- Ask for confirmation before writes such as creating links, marking no-shows, or changing webhooks.
- If Calendly is not connected, direct the user to https://claw-link.dev/dashboard?add=calendly.
- Never echo or repeat the user's ClawLink credential.

## Resources

- ClawLink: https://claw-link.dev
- ClawLink Docs: https://docs.claw-link.dev/openclaw
- ClawLink Verification: https://claw-link.dev/verify
- ClawLink Source: https://github.com/hith3sh/clawlink
- Calendly API: https://developer.calendly.com/
openclaw clawlink hermes

Comments

Sign in to leave a comment

Loading comments...