---
title: "Connect Calendly and Sorry - APIANT.ai"
description: "When \"New scheduled event (polling)\" fires in Calendly, your agent runs \"Update status page\" in Sorry."
canonical: "https://apiant.ai/connect/calendly-to-sorry"
---

# Connect Calendly and Sorry

When **New scheduled event (polling)** fires in [Calendly](https://apiant.ai/connections/calendly), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Update event type availability schedule** in Calendly. Describe the whole flow and it is built, tested on every scenario and kept running.

Calendly **2** triggers Calendly **18** actions Sorry **1** trigger Sorry **16** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Calendly and Sorry to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Calendly and Sorry can do together

### From Calendly to Sorry

- When **New scheduled event (polling)** in Calendly then **Update status page** in Sorry
- When **Canceled scheduled event (polling)** in Calendly then **Add component** in Sorry

### From Sorry to Calendly

- When **New notice** in Sorry then **Update event type availability schedule** in Calendly
- When **New notice** in Sorry then **Get current user** in Calendly

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Calendly and Sorry

## Triggers and actions 3 triggers · 34 actions

- Trigger

**Canceled scheduled event (polling)**

Triggers when a scheduled event is canceled.

- Trigger

**New scheduled event (polling)**

Triggers when a new scheduled event is created.

- Action

**Cancel scheduled event**

Cancels a scheduled event with a specified reason for the cancellation.

- Action

**Create single-use scheduling link**

Creates a single-use booking link that allows one person to schedule an event.

- Action

**Get current user**

Returns the authenticated user's profile including name, email, timezone, and scheduling URL.

- Action

**Get event type**

Returns details for the specified event type.

- Action

**Get invitee**

Returns details about a specific invitee for a scheduled event.

- Action

**Get invitee next scheduled event**

Gets the next scheduled event for the invitee specified by their email.

- Action

**Get scheduled event**

Returns details about a specific scheduled event.

- Action

**Get user availability schedule**

Returns details for the specified user availability schedule.

- Action

**List event invitees**

Returns the list of invitees for a scheduled event, optionally filtered by status.

- Action

**List event type availability schedules**

Returns the event type's availability schedules.

- Action

**List event types**

Returns your calendar's event type templates, optionally filtered by scope and active status.

- Action

**List organization memberships**

Returns all members of the connected Calendly organization (paginated). One record per membership: user_email, user_uri, user_name, role.

- Action

**List scheduled events**

Returns scheduled events, filterable by scope, status, date range, and invitee email.

- Action

**List user availability schedules**

Returns the user's availability schedules.

- Action

**List webhook subscriptions**

Returns all webhook subscriptions for your organization.

- Action

**Mark invitee as no-show**

Records that an invitee did not attend their scheduled event.

- Action

**Undo invitee no-show**

Removes a no-show marking from an invitee.

- Action

**Update event type availability schedule**

Replaces a single host's availability schedule on a Calendly event type with explicit date rules (full overwrite). Built for CalendarConnect: push real Mindbody bookable slots into Calendly so only MBO-bookable times are offered. CRITICAL: the host is targeted by the NESTED availability_rule.user — a top-level user alone is silently ignored and Calendly replaces the OAuth token owner's schedule instead. Always verify stored_user equals the requested host before trusting the result. For round-robin events, call once per host.

- Trigger

**New notice**

Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.

- Action

**Add component**

Creates a new component on a Sorry status page, optionally nested under a parent component.

- Action

**Add notice**

Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.

- Action

**Add notice update**

Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.

- Action

**Add subscriber**

Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.

- Action

**Delete notice**

Deletes a notice (incident, maintenance or general) from a Sorry status page.

- Action

**Delete subscriber**

Permanently removes a subscriber from a status page.

- Action

**Get notice**

Returns a single notice from a status page, including its type, state, subject, synopsis and link.

- Action

**Get status page**

Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.

- Action

**List components**

Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.

- Action

**List notices**

Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.

- Action

**List notice updates**

Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.

- Action

**List status pages**

Returns all status pages in your Sorry account, optionally filtered by name or creation date.

- Action

**List subscribers**

Returns the subscribers on a status page, optionally only those who receive notices for a specific component.

- Action

**Update component**

Updates a component on a Sorry status page, such as its name, description, position or parent component.

- Action

**Update notice**

Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.

- Action

**Update status page**

Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.

## Each app on its own

- [ **Calendly** Calendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...](https://apiant.ai/connections/calendly)
- [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry)

Reviews

## What our customers say

## More from Calendly

- [ **Calendly to Notion** A new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.](https://apiant.ai/connect/calendly-to-notion)
- [ **Calendly to GoHighLevel** All-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...](https://apiant.ai/connect/calendly-to-gohighlevel)
- [ **Calendly to CORE** Access the world's Open Access research papers](https://apiant.ai/connect/calendly-to-core)
- [ **Calendly to Fera** Fera is a customer reviews app that allows you to automate review requests, display reviews on your site and...](https://apiant.ai/connect/calendly-to-fera)
- [ **Calendly to Fidel Api** API for linking bank cards and streaming real-time card transaction data to power loyalty and rewards...](https://apiant.ai/connect/calendly-to-fidel-api)
- [ **Calendly to Webscraper Io** Cloud web scraping platform with a REST API for extracting data from websites, including JS-rendered pages...](https://apiant.ai/connect/calendly-to-webscraper-io)

## More into Sorry

- [ **HubSpot to Sorry** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sorry)
- [ **Salesforce to Sorry** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sorry)
- [ **Slack to Sorry** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sorry)
- [ **Google Sheets to Sorry** Google Sheets](https://apiant.ai/connect/google-sheets-to-sorry)
- [ **Gmail to Sorry** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sorry)
- [ **Google Calendar to Sorry** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sorry)

Questions

## Calendly and Sorry, answered

###

### What can start an automation from Calendly?

Any of Calendly's 2 triggers in the catalog, including New scheduled event (polling) and Canceled scheduled event (polling). Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Sorry when something happens in Calendly?

Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Sorry to Calendly?

Yes. When something happens in Sorry, your agent can act in Calendly too. This page covers both directions: Sorry's triggers and Calendly's actions are listed here as well.

###

### Do I have to build a connector for Calendly or Sorry?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Calendly and Sorry without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
