---
title: "Connect Jitbit Helpdesk and Sorry - APIANT.ai"
description: "When \"New Ticket\" fires in Jitbit Helpdesk, your agent runs \"Update status page\" in Sorry."
canonical: "https://apiant.ai/connect/jitbit-helpdesk-to-sorry"
---

# Connect Jitbit Helpdesk and Sorry

When **New Ticket** fires in [Jitbit Helpdesk](https://apiant.ai/connections/jitbit-helpdesk), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Add tag to ticket** in Jitbit Helpdesk. Describe the whole flow and it is built, tested on every scenario and kept running.

Jitbit Helpdesk **1** trigger Jitbit Helpdesk **19** 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 Jitbit Helpdesk 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 Jitbit Helpdesk and Sorry can do together

### From Jitbit Helpdesk to Sorry

- When **New Ticket** in Jitbit Helpdesk then **Update status page** in Sorry
- When **New Ticket** in Jitbit Helpdesk then **Add component** in Sorry

### From Sorry to Jitbit Helpdesk

- When **New notice** in Sorry then **Add tag to ticket** in Jitbit Helpdesk
- When **New notice** in Sorry then **Create Ticket** in Jitbit Helpdesk

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 Jitbit Helpdesk and Sorry

## Triggers and actions 2 triggers · 35 actions

- Trigger

**New Ticket**

Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.

- Action

**Add article**

Creates a new knowledge base article in a category.

- Action

**Add asset**

Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.

- Action

**Add company**

Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.

- Action

**Add tag to ticket**

Adds a tag to a ticket. The tag is created if it does not already exist.

- Action

**Add time spent**

Logs a time spent entry on a ticket under the connected user. Requires technician permissions.

- Action

**Create New Reply**

Posts a new reply (comment) to an existing helpdesk ticket.

- Action

**Create Ticket**

Creates a new helpdesk ticket in a category, with a subject, body and priority.

- Action

**Create User**

Creates a new helpdesk user. Requires administrator permissions.

- Action

**Find Ticket**

Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.

- Action

**Find User**

Finds a helpdesk user by their email address and returns their profile.

- Action

**Get Article**

Returns a knowledge base article with its full content, category, tags and attachments.

- Action

**Get ticket**

Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.

- Action

**List Companies**

Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.

- Action

**List Ticket Comments**

Returns all comments (replies) posted on a Jitbit Helpdesk ticket.

- Action

**List tickets**

Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.

- Action

**List Time Spent Entries**

Returns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions.

- Action

**Update company**

Updates a company's name, notes and email domains in Jitbit Helpdesk.

- Action

**Update ticket**

Updates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body.

- Action

**Update user**

Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.

- 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

- [ **Jitbit Helpdesk** A great help desk app for small and medium sized companies.](https://apiant.ai/connections/jitbit-helpdesk)
- [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry)

Reviews

## What our customers say

## More from Jitbit Helpdesk

- [ **Jitbit Helpdesk to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/jitbit-helpdesk-to-salesforce)
- [ **Jitbit Helpdesk to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/jitbit-helpdesk-to-slack)
- [ **Jitbit Helpdesk to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/jitbit-helpdesk-to-mailchimp)
- [ **Jitbit Helpdesk to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/jitbit-helpdesk-to-stripe)
- [ **Jitbit Helpdesk to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/jitbit-helpdesk-to-shopify)
- [ **Jitbit Helpdesk to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/jitbit-helpdesk-to-quickbooks-online)

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

## Jitbit Helpdesk and Sorry, answered

###

### What can start an automation from Jitbit Helpdesk?

Any of Jitbit Helpdesk's 1 trigger in the catalog, including New Ticket. Describe the moment in plain language and your agent picks the right one.

###

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

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 Jitbit Helpdesk?

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

###

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