---
title: "Connect folk and Sorry - APIANT.ai"
description: "When \"Company Added\" fires in folk, your agent runs \"Update status page\" in Sorry, or \"New notice\" in Sorry to \"Create Deal\" in folk."
canonical: "https://apiant.ai/connect/folk-to-sorry"
---

# Connect folk and Sorry

When **Company Added** fires in [folk](https://apiant.ai/connections/folk), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Create Deal** in folk. Describe the whole flow and it is built, tested on every scenario and kept running.

folk **11** triggers folk **16** 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 folk 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 folk and Sorry can do together

### From folk to Sorry

- When **Company Added** in folk then **Update status page** in Sorry
- When **Company Custom Field Updated** in folk then **Add component** in Sorry

### From Sorry to folk

- When **New notice** in Sorry then **Create Deal** in folk
- When **New notice** in Sorry then **Create Note** in folk

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 folk and Sorry

## Triggers and actions 12 triggers · 32 actions

- Trigger

**Company Added**

Triggers when a new company is created or added to a group.

- Trigger

**Company Custom Field Updated**

Triggers when a company custom field (for example tag, status, text, assignee) is updated.

- Trigger

**Company Removed**

Triggers when a company is deleted from the workspace or removed from a group.

- Trigger

**Company Updated**

Triggers when a company basic field (like name, email or URL) in a group is updated.

- Trigger

**Deal Added**

Fires when a new deal is created.

- Trigger

**Deal Removed**

Fires when a deal is deleted from a pipeline.

- Trigger

**Deal Updated**

Fires when a deal is updated (stage change, field update).

- Trigger

**Person Added**

Triggers when a new person is created or added to a group.

- Trigger

**Person Custom Field Updated**

Triggers when a person custom field (for example tag, status, text, assignee) is updated.

- Trigger

**Person Removed**

Triggers when a person is deleted from the workspace or removed from a group.

- Trigger

**Person Updated**

Triggers when a person basic field (like first name, job title, email or URL) in a group is updated.

- Action

**Create Company**

Creates a company in folk, optionally adding it to a group and setting that group's custom fields.

- Action

**Create Deal**

Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields.

- Action

**Create Group**

Creates a group in folk. A default "All people" table view is added to the group automatically.

- Action

**Create Note**

Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note.

- Action

**Create Person**

Creates a person in folk, optionally adding them to a group and setting that group's custom fields.

- Action

**Create Reminder**

Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule.

- Action

**Delete Company**

Deletes a company from folk by its id.

- Action

**Delete Person**

Deletes a person from folk by their id. This also removes their custom fields, notes and associations.

- Action

**Find a Company**

Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping.

- Action

**Find a Person**

Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping.

- Action

**Get a Company**

Fetches one folk company by id, including its custom field values.

- Action

**Get a Note**

Fetches one folk note by id, with its text, author and the record it is attached to.

- Action

**Get a Person**

Fetches one folk person by id, including their custom field values.

- Action

**List Groups**

Returns the groups in the folk workspace, with each group's id, name and visibility.

- Action

**Update Company**

Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list.

- Action

**Update Person**

Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list.

- 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

- [ **folk** folk is the next generation CRM for teams](https://apiant.ai/connections/folk)
- [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry)

Reviews

## What our customers say

## More from folk

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

## 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

## folk and Sorry, answered

###

### What can start an automation from folk?

Any of folk's 11 triggers in the catalog, including Company Added, Company Custom Field Updated, Company Removed and Company Updated. Describe the moment in plain language and your agent picks the right one.

###

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

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 folk?

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

###

### Do I have to build a connector for folk 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 folk 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.
