Integration
Connect Sorry and Zite
When New notice fires in Sorry, your agent runs Create Record in Zite, or New Field in Zite to Update status page in Sorry. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Sorry and Zite to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Sorry and Zite can do together
From Sorry to Zite
When New notice in Sorry
then Create Record in Zite
When New notice in Sorry
then Update Record in Zite
From Zite to Sorry
When New Field in Zite
then Update status page in Sorry
When New Record in Zite
then Add component in Sorry
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 Sorry and Zite
Triggers and actions 10 triggers · 28 actions
Trigger
New noticeTriggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.
Action
Add componentCreates a new component on a Sorry status page, optionally nested under a parent component.
Action
Add noticeCreates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.
Action
Add notice updatePosts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.
Action
Add subscriberAdds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.
Action
Delete noticeDeletes a notice (incident, maintenance or general) from a Sorry status page.
Action
Delete subscriberPermanently removes a subscriber from a status page.
Action
Get noticeReturns a single notice from a status page, including its type, state, subject, synopsis and link.
Action
Get status pageReturns 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 componentsReturns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.
Action
List noticesReturns 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 updatesReturns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.
Action
List status pagesReturns all status pages in your Sorry account, optionally filtered by name or creation date.
Action
List subscribersReturns the subscribers on a status page, optionally only those who receive notices for a specific component.
Action
Update componentUpdates a component on a Sorry status page, such as its name, description, position or parent component.
Action
Update noticeUpdates 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 pageUpdates a status page's settings, such as its name, timezone, support contact details, search visibility and language.
Trigger
Deleted FieldTriggers when a field is deleted from a table.
Trigger
Deleted RecordTriggers when a record is deleted from a table.
Trigger
Deleted TableTriggers when a table is deleted from a base.
Trigger
New FieldTriggers when a new field is created in a table.
Trigger
New RecordTriggers when a new record is created in a table.
Trigger
New TableTriggers when a new table is created in a base.
Trigger
Updated FieldTriggers when a field is updated in a table.
Trigger
Updated RecordTriggers when an existing record is updated in a table.
Trigger
Updated TableTriggers when a table is updated in a base.
Action
Create FieldCreates a new field in a table.
Action
Create RecordCreates a new record in a table.
Action
Create TableCreates a new table in a base.
Action
Delete FieldDeletes a field from a table.
Action
Delete RecordDeletes a record from a table.
Action
Delete TableDeletes a table from a base.
Action
Find FieldFinds a field by name.
Action
Find RecordFinds a record by field value.
Action
Find TableFinds a table by name.
Action
Update FieldUpdates a field's name or settings.
Action
Update RecordUpdates an existing record in a table.
Action
Update TableUpdates a table's name or description.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Sorry
Sorry to StripeStripe is a payment processing platform for online businesses.
Sorry to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Sorry to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Sorry to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Sorry to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Sorry to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Zite
HubSpot to ZiteHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ZiteSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ZiteSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ZiteGoogle Sheets
Gmail to ZiteGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ZiteGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Sorry and Zite, answered
What can start an automation from Sorry?
Any of Sorry's 1 trigger in the catalog, including New notice. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Zite when something happens in Sorry?
Any of Zite's 12 actions, including Create Field, Create Record, Create Table and Update Field. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Zite to Sorry?
Yes. When something happens in Zite, your agent can act in Sorry too. This page covers both directions: Zite's triggers and Sorry's actions are listed here as well.
Do I have to build a connector for Sorry or Zite?
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 Sorry and Zite 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.