> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to CalendarHero

The CalendarHero connector lets your AI agent act in each user's CalendarHero account. Each user connects their own CalendarHero API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 33 tools.

**Authentication:** API Key
**Categories:** Calendar, Productivity
**Tools:** 33: 18 read, 11 write, 4 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CALENDARHERO)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the CalendarHero connection

   In **AgentKit > Connections**, create a CalendarHero connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'calendarhero'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize CalendarHero:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'calendarhero_assistant_reply_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "calendarhero"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize CalendarHero:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="calendarhero_assistant_reply_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their CalendarHero credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'calendarhero_assistant_reply_get',
  toolInput: {},
  connector: 'calendarhero',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="calendarhero_assistant_reply_get",
    tool_input={},
    connection_name="calendarhero",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `calendarhero_assistant_reply_get`

Get Assistant Reply · Read-only

Get the CalendarHero assistant's latest reply message for the user.
Returns the reply text and any options.
Use Send Assistant Message first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calendarhero_contact_get`

Get Contact · Read-only

Get one contact by ID, with insights unless basic is set.
Returns the contact's name, emails, phones, title, organization and insights.
Use Search Contacts to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`string`, required): CalendarHero contact ID, from Search Contacts. Example: 5f3a1b2c4d5e6f7890123456.
- `basic` (`boolean`, optional): true returns only the data stored in CalendarHero; false (default) also returns contact insights. Example: true.

Example input: `{"contact_id":"<contact_id>"}`

### `calendarhero_contacts_count`

Count Contacts · Read-only

Count the user's contacts.
Returns the number of contacts.
Use Search Contacts to list them.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calendarhero_contacts_search`

Search Contacts · Read-only

Search the user's contacts by email, domain or name, or list popular, recent or by-letter contacts.
Returns matching contacts with id, name, emails, title and organization.
Use Get Contact for one contact's insights.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `all` (`string`, optional): 1 to keep duplicate contacts, 0 to remove them (default). Example: 0. One of: `1`, `0`.
- `filter` (`string`, optional): Preset set of contacts instead of a search: popular, recent, or a single letter a to z for names starting with it. Example: recent. One of: `popular`, `recent`, `a`, `b`, `c`, `d`, `e`, `f`, `g`, `h`, `i`, `j`, `k`, `l`, `m`, `n`, `o`, `p`, `q`, `r`, `s`, `t`, `u`, `v`, `w`, `x`, `y`, `z`.
- `include_teams` (`string`, optional): 1 to also return matching teams. Example: 0. One of: `1`, `0`.
- `search` (`string`, optional): Email (name@domain.com), domain (@domain.com) or name (First Last) to match. Not used with filter. Example: @acme.com.

Example input: `{}`

### `calendarhero_directories_list`

List Connected Directories · Read-only

List the calendars, contact books and other services the user has connected to CalendarHero.
Returns each connection with its id, provider type, category types and import dates.
Use Get Connected Directory for one connection.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calendarhero_directory_get`

Get Connected Directory · Read-only

Get one connected calendar, contact book or other service by its ID.
Returns its provider type, category types, name and import dates.
Use List Connected Directories to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `directory_id` (`string`, required): Directory (connection) UUID, from List Connected Directories. Example: 6a1f2c3d-4b5e-6f70-8a9b-0c1d2e3f4a5b.

Example input: `{"directory_id":"<directory_id>"}`

### `calendarhero_integrations_list`

List Integrations · Read-only

List the integration providers CalendarHero supports, optionally by category.
Returns each provider with its type and name.
Use List Connected Directories for the services the user has connected.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `org` (`boolean`, optional): Return the organization's integrations instead of the user's. Example: false.
- `type` (`string`, optional): Only integrations of this category, for example calendar, contacts, video or crm. Example: calendar. One of: `calendar`, `contacts`, `messaging`, `social`, `email`, `search`, `files`, `groups`, `faq`, `crm`, `ticket`, `rooms`, `video`, `ats`, `payment`.

Example input: `{}`

### `calendarhero_meeting_categories_get`

Get Meeting Categories · Read-only

Get stats on the user's meetings by category for a month.
Returns meeting counts and time per category.
Use List Meetings for the meetings themselves.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `month` (`string`, optional): Month as YYYY-MM. Example: 2026-11.

Example input: `{}`

### `calendarhero_meeting_requests_list`

List Meeting Requests · Read-only

List the meeting requests (scheduling tasks) CalendarHero is handling for the user.
Returns requests with id, subject, contacts, type, state and proposed times.
Use Create Meeting Request to start a new one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `skip` (`number`, optional): Number of requests to skip, for paging. Example: 0.
- `state` (`string`, optional): Only requests in this state: active, upcoming or closed. Example: active. One of: `active`, `upcoming`, `closed`.
- `take` (`number`, optional): Number of requests to return. Example: 25.
- `tally` (`boolean`, optional): Return counts instead of the requests. Example: false.
- `type` (`string`, optional): Only requests of this meeting type. Example: call.

Example input: `{}`

### `calendarhero_meeting_types_list`

List Meeting Types · Read-only

List the user's meeting types (such as call, coffee or lunch) and their settings.
Returns each meeting type with its name, duration, locations and options.
Use a type name in Create Meeting Request.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `only_types` (`boolean`, optional): Return only the meeting type definitions, without other meeting settings. Example: true.

Example input: `{}`

### `calendarhero_meetings_list`

List Meetings · Read-only

List the user's calendar meetings within a time window.
Returns meetings with subject, start and end, attendees and location.
Use List Meeting Requests for meetings CalendarHero is still scheduling.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `end` (`string`, required): End of the time window (ISO 8601 date-time). Example: 2026-11-23T00:00:00Z.
- `start` (`string`, required): Start of the time window (ISO 8601 date-time). Example: 2026-11-16T00:00:00Z.

Example input: `{"end":"<end>","start":"<start>"}`

### `calendarhero_search`

Search Integrations · Read-only

Search all of the user's connected services (email, files, CRM and others) for a term.
Returns matching results grouped by service, with result IDs.
Use Get Search Result for one result's details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): Term to search for across the user's connected services. Example: Acme proposal.
- `date_end` (`string`, optional): End of the time window (YYYY-MM-DDTHH:mm:ssZ). Example: 2026-11-16T23:59:59Z.
- `date_start` (`string`, optional): Start of the time window (YYYY-MM-DDTHH:mm:ssZ). Example: 2026-10-01T00:00:00Z.

Example input: `{"query":"<query>"}`

### `calendarhero_search_result_get`

Get Search Result · Read-only

Get one search result's details.
Returns the full result content and source.
Use Search Integrations first to get the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `result_id` (`string`, required): ID of a result returned by Search Integrations. Example: 6a1f2c3d4b5e6f708a9b0c1d.

Example input: `{"result_id":"<result_id>"}`

### `calendarhero_user_get`

Get User · Read-only

Get the CalendarHero user tied to the API token.
Returns the user's profile, settings, meeting preferences and connected services.
Use it to check the token works and read scheduling settings.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calendarhero_user_org_get`

Get Organization · Read-only

Get the organization the CalendarHero user belongs to.
Returns the organization's details and, optionally, billing user info.
Use Get User for the user's own profile.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `return_billing_user_info` (`boolean`, optional): Also return the organization's billing user details. Example: false.

Example input: `{}`

### `calendarhero_user_savings_get`

Get Time Savings · Read-only

Get the user's CalendarHero time-savings figures.
Returns how much scheduling time CalendarHero has saved the user.
Use Get Meeting Categories for meeting stats by category.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calendarhero_webhook_sample_get`

Get Webhook Sample · Read-only

Get a sample payload for a CalendarHero webhook event.
Returns an example of the JSON CalendarHero posts for that event.
Use it to build a receiver before subscribing.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event` (`string`, required): Webhook event: meeting_request_success, new_meeting_request, meeting_request_expired, meeting_request_cancelled, meeting_rescheduled, new_contact_added, meeting_completed or meeting_started. Example: new_meeting_request. One of: `meeting_request_success`, `new_meeting_request`, `meeting_request_expired`, `meeting_request_cancelled`, `meeting_rescheduled`, `new_contact_added`, `meeting_completed`, `meeting_started`.

Example input: `{"event":"meeting_request_success"}`

### `calendarhero_webhooks_list`

List Webhooks · Read-only

List the webhook URLs subscribed to one CalendarHero event.
Returns the hook URLs for that event.
Use Subscribe Webhook to add one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event` (`string`, required): Webhook event: meeting_request_success, new_meeting_request, meeting_request_expired, meeting_request_cancelled, meeting_rescheduled, new_contact_added, meeting_completed or meeting_started. Example: new_meeting_request. One of: `meeting_request_success`, `new_meeting_request`, `meeting_request_expired`, `meeting_request_cancelled`, `meeting_rescheduled`, `new_contact_added`, `meeting_completed`, `meeting_started`.

Example input: `{"event":"meeting_request_success"}`

### `calendarhero_assistant_message_send`

Send Assistant Message · Write

Send a plain-language message to the CalendarHero scheduling assistant, as in the web chat.
Returns the assistant's acknowledgement; it may act on the request.
Use Get Assistant Reply to read its reply.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `text` (`string`, required): Message to the CalendarHero assistant, in plain language. Example: Schedule a call with jane@acme.com next week.

Example input: `{"text":"<text>"}`

### `calendarhero_contact_create`

Create Contact · Write

Create a contact in CalendarHero.
Returns the new contact with its id.
Use Search Contacts first to avoid duplicates.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`array`, required): The contact's email addresses. Example: ["jane@acme.com"].
- `default_email` (`string`, optional): Which of the emails to use by default. Example: jane@acme.com.
- `name` (`string`, optional): Contact name as "First Last". Example: Jane Doe.
- `organization` (`string`, optional): Company or organization. Example: Acme Corp.
- `telephone` (`array`, optional): Phone numbers. Example: ["+14155550123"].
- `title` (`string`, optional): Job title. Example: VP Sales.

Example input: `{"email":["jane@acme.com"]}`

### `calendarhero_contact_update`

Update Contact · Write

Update a contact's name, emails, phones, title or organization.
Returns the updated contact.
Send the full email list; email is required.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`string`, required): CalendarHero contact ID, from Search Contacts. Example: 5f3a1b2c4d5e6f7890123456.
- `email` (`array`, required): The contact's email addresses. Example: ["jane@acme.com"].
- `default_email` (`string`, optional): Which of the emails to use by default. Example: jane@acme.com.
- `name` (`string`, optional): Contact name as "First Last". Example: Jane Doe.
- `organization` (`string`, optional): Company or organization. Example: Acme Corp.
- `telephone` (`array`, optional): Phone numbers. Example: ["+14155550123"].
- `title` (`string`, optional): Job title. Example: VP Sales.

Example input: `{"contact_id":"<contact_id>","email":["jane@acme.com"]}`

### `calendarhero_meeting_request_create`

Create Meeting Request · Write

Ask CalendarHero to schedule a meeting with contacts within a date window.
Returns the new meeting request; CalendarHero emails the contacts to find a time.
Use List Meeting Requests to follow it. Use Remind Meeting Request to nudge contacts.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `date_end` (`string`, required): End of the window to schedule in (YYYY-MM-DDTHH:mm:ssZ). The date part is the last day to consider. Example: 2026-11-21T23:59:59Z.
- `date_start` (`string`, required): Start of the window to schedule in (YYYY-MM-DDTHH:mm:ssZ). The date part is the first day to consider. Example: 2026-11-17T00:00:00Z.
- `subject` (`string`, required): Meeting topic or subject. Example: Quarterly review.
- `capacity` (`number`, optional): Seats needed in a meeting room. 0 books no room. Example: 0.
- `contact_emails` (`array`, optional): Emails of the people to meet. Example: ["jane@acme.com"].
- `contacts` (`array`, optional): CalendarHero contacts to meet, each as an object with the contact id from Search Contacts. Example: [{"id": "5f3a1b2c4d5e6f7890123456"}].
- `description` (`string`, optional): Meeting agenda or description. Example: Review Q4 targets..
- `location` (`string`, optional): Meeting location. Example: Zoom.
- `meeting_length` (`number`, optional): Meeting length in minutes. Defaults to the meeting type's duration. Example: 30.
- `type` (`string`, optional): Meeting type name, from List Meeting Types. Example: call.

Example input: `{"date_end":"<date_end>","date_start":"<date_start>","subject":"<subject>"}`

### `calendarhero_meeting_request_remind`

Remind Meeting Request · Write

Send the contacts of a pending meeting request a reminder.
Returns a confirmation. Sends email to the contacts.
Use List Meeting Requests to find the request ID.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `task_id` (`string`, required): Meeting request (task) ID, from List Meeting Requests. Example: 60b8d2f4e1a2b3c4d5e6f789.

Example input: `{"task_id":"<task_id>"}`

### `calendarhero_meeting_type_create`

Create Meeting Type · Write

Add a new meeting type with the given name to the user.
Returns the new meeting type.
Use Update Meeting Types to change its settings afterwards.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `meeting_type` (`string`, required): Meeting type name, as returned by List Meeting Types (for example call or coffee). Example: call.

Example input: `{"meeting_type":"<meeting_type>"}`

### `calendarhero_meeting_type_share`

Share Meeting Type · Write

Share one of the user's meeting types with the rest of the organization.
Returns the sharing result.
Use List Meeting Types to find the name.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `meeting_type` (`string`, required): Meeting type name, as returned by List Meeting Types (for example call or coffee). Example: call.
- `share_with` (`string`, required): Who to share with: with-all-users (current organization users) or with-all-and-new-users (also future users). Example: with-all-users. One of: `with-all-users`, `with-all-and-new-users`.

Example input: `{"meeting_type":"<meeting_type>","share_with":"with-all-users"}`

### `calendarhero_meeting_types_update`

Update Meeting Types · Write

Save the user's meeting type settings.
Returns the updated meeting types.
Use List Meeting Types first and send back the edited list.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `meeting_types` (`array`, required): The full list of meeting type objects to save, in the shape List Meeting Types returns. Fetch them first and send back the edited list. Example: [{"name": "call"}].

Example input: `{"meeting_types":[{"name":"call"}]}`

### `calendarhero_user_address_update`

Update Address Location · Write

Set the geographic location of the user's address, used for travel time and in-person meetings.
Returns the updated settings.
Use Get User to read the current settings.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `lat` (`string`, required): Latitude of the user's address. Example: 37.7749.
- `lng` (`string`, required): Longitude of the user's address. Example: -122.4194.

Example input: `{"lat":"<lat>","lng":"<lng>"}`

### `calendarhero_user_restricted_apps_update`

Update Restricted Apps · Write

Set which connected apps CalendarHero must not use for the user.
Returns the updated settings.
Use List Integrations to see app names.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `restricted_apps` (`array`, required): Names of the integrations or apps CalendarHero must not use for this user. Example: ["slack"].

Example input: `{"restricted_apps":["slack"]}`

### `calendarhero_webhook_subscribe`

Subscribe Webhook · Write

Subscribe a URL to a CalendarHero event, such as a new meeting request or a completed meeting.
Returns the subscription.
Use Get Webhook Sample to see the payload.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `event` (`string`, required): Webhook event: meeting_request_success, new_meeting_request, meeting_request_expired, meeting_request_cancelled, meeting_rescheduled, new_contact_added, meeting_completed or meeting_started. Example: new_meeting_request. One of: `meeting_request_success`, `new_meeting_request`, `meeting_request_expired`, `meeting_request_cancelled`, `meeting_rescheduled`, `new_contact_added`, `meeting_completed`, `meeting_started`.
- `hook_url` (`string`, required): HTTPS URL that receives the webhook POSTs. Example: https://example.com/hooks/calendarhero.

Example input: `{"event":"meeting_request_success","hook_url":"<hook_url>"}`

### `calendarhero_contact_delete`

Delete Contact · Destructive

Delete a contact from CalendarHero.
Returns a confirmation.
Use Search Contacts to find the ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`string`, required): CalendarHero contact ID, from Search Contacts. Example: 5f3a1b2c4d5e6f7890123456.

Example input: `{"contact_id":"<contact_id>"}`

### `calendarhero_meeting_request_delete`

Delete Meeting Request · Destructive

Delete (cancel) a meeting request.
Returns a confirmation.
Use List Meeting Requests to find the request ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `task_id` (`string`, required): Meeting request (task) ID, from List Meeting Requests. Example: 60b8d2f4e1a2b3c4d5e6f789.

Example input: `{"task_id":"<task_id>"}`

### `calendarhero_meeting_type_delete`

Delete Meeting Type · Destructive

Delete one of the user's meeting types by name.
Returns the remaining meeting types.
Use List Meeting Types to find the name.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `meeting_type` (`string`, required): Meeting type name, as returned by List Meeting Types (for example call or coffee). Example: call.

Example input: `{"meeting_type":"<meeting_type>"}`

### `calendarhero_webhook_unsubscribe`

Unsubscribe Webhook · Destructive

Remove a URL's subscription to a CalendarHero event.
Returns a confirmation.
Use List Webhooks to see subscribed URLs.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `event` (`string`, required): Webhook event: meeting_request_success, new_meeting_request, meeting_request_expired, meeting_request_cancelled, meeting_rescheduled, new_contact_added, meeting_completed or meeting_started. Example: new_meeting_request. One of: `meeting_request_success`, `new_meeting_request`, `meeting_request_expired`, `meeting_request_cancelled`, `meeting_rescheduled`, `new_contact_added`, `meeting_completed`, `meeting_started`.
- `hook_url` (`string`, required): HTTPS URL that receives the webhook POSTs. Example: https://example.com/hooks/calendarhero.

Example input: `{"event":"meeting_request_success","hook_url":"<hook_url>"}`

## Related

Other Calendar connectors ([all 25](/agentkit/connectors/?category=calendar)):

- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools
- [Zoom](/agentkit/connectors/zoom/): Scalekit connector, OAuth, 58 tools
- [Calendly](/agentkit/connectors/calendly/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
