---
title: "Connect Busybusy and Sorry - APIANT.ai"
description: "When \"Certifications: Certification Updated\" fires in Busybusy, your agent runs \"Update status page\" in Sorry."
canonical: "https://apiant.ai/connect/busybusy-to-sorry"
---

# Connect Busybusy and Sorry

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

Busybusy **6** triggers Busybusy **27** 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 Busybusy 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 Busybusy and Sorry can do together

### From Busybusy to Sorry

- When **Certifications: Certification Updated** in Busybusy then **Update status page** in Sorry
- When **Certifications: New Certification Created** in Busybusy then **Add component** in Sorry

### From Sorry to Busybusy

- When **New notice** in Sorry then **Create Project** in Busybusy
- When **New notice** in Sorry then **Create Break Entry** in Busybusy

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

## Triggers and actions 7 triggers · 43 actions

- Trigger

**Certifications: Certification Updated**

Triggers when a certification is created or updated in Busybusy.

- Trigger

**Certifications: New Certification Created**

Triggers when a new certification type is created in Busybusy.

- Trigger

**Employee Created**

Triggers when a new employee (member) is added to your busybusy organization.

- Trigger

**Employee Updated**

Triggers when an employee in busybusy is created or changed.

- Trigger

**Project Created**

Triggers when a new project is created in busybusy.

- Trigger

**Project Updated**

Triggers when a project or subproject is created or changed in Busybusy, including when it is unarchived.

- Action

**Archive Employee**

Archives an employee (member) in busybusy by setting their archived date.

- Action

**Archive Project**

Archives a project in Busybusy by setting its archived date.

- Action

**Certifications: Create Certification**

Creates a certification type in your Busybusy organization that employees can later be certified against.

- Action

**Certifications: Create Employee Certification**

Records that an employee holds a certification, with its issue, renewal and expiry dates.

- Action

**Certifications: Delete Certification**

Deletes a certification from your Busybusy organization by marking it deleted.

- Action

**Certifications: Renew Employee Certification**

Renews an employee's certification record in busybusy by setting a new renewal date and, optionally, a new expiration date.

- Action

**Certifications: Search Certifications**

Searches certifications in Busybusy by name, ID or date filters and returns the matching certifications.

- Action

**Certifications: Update Certification**

Updates an existing certification's name, description, renewal period or documentation settings.

- Action

**Certifications: Update Employee Certification**

Updates an employee's certification record in busybusy, such as its issue, renewal or expiration date or the employee it belongs to.

- Action

**Create Break Entry**

Creates a break on an existing busybusy time entry, with its start time and optional end time.

- Action

**Create Budget**

Creates a cost budget for a busybusy project, optionally scoped to a cost code or piece of equipment.

- Action

**Create Cost Code Group**

Creates a cost code group in busybusy for organizing cost codes.

- Action

**Create Employee**

Creates a new employee (member) in your busybusy organization.

- Action

**Create Equipment**

Creates a piece of equipment in busybusy with its name, model, serial number and tracking options.

- Action

**Create Project**

Creates a new project in busybusy.

- Action

**Create Time Entry**

Creates a time entry (clock-in record) for an employee in busybusy, optionally against a project, cost code and equipment.

- Action

**Search Break Entries**

Returns the break entries that match the filters you supply, such as a time entry, start time or paid status.

- Action

**Search Employee (Single)**

Finds a single employee by ID and returns the first matching employee record.

- Action

**Search Employees (Multiple)**

Returns the employees that match the filters you supply, such as name, username, employee number or group.

- Action

**Search Projects (Multiple)**

Returns all projects matching the given title, parent project, ID or dates.

- Action

**Unarchive Cost Code**

Restores an archived cost code so it is active again.

- Action

**Unarchive Employee**

Restores an archived employee in busybusy so they are active again.

- Action

**Unarchive Project**

Restores an archived project in Busybusy so it is active again.

- Action

**Update Cost Code**

Updates an existing cost code's title, code, unit, group, insurance classes or custom fields.

- Action

**Update Employee**

Updates an existing busybusy employee's name, username, contact details, position, employee number or group.

- Action

**Update Equipment**

Updates an existing piece of equipment in busybusy, changing only the details you fill in.

- Action

**Update Project**

Updates an existing project's name, parent project, or archive date in busybusy.

- 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

- [ **Busybusy** Busybusy is the perfect time tracking & job costing app built BY construction companies FOR construction...](https://apiant.ai/connections/busybusy)
- [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry)

Reviews

## What our customers say

## More from Busybusy

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

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

## Busybusy and Sorry, answered

###

### What can start an automation from Busybusy?

Any of Busybusy's 6 triggers in the catalog, including Certifications: Certification Updated, Certifications: New Certification Created, Employee Created and Employee 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 Busybusy?

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

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

###

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