Integration
Connect Sorry to Support Board
When New notice fires in Sorry, your agent runs Send Message in Support Board. 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 Support Board 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 can start in Support Board
When New notice in Sorry
then Send Message in Support Board
When New notice in Sorry
then Update Message in Support Board
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 Support Board
Triggers and actions 1 trigger · 51 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
Add ConversationCreates a new conversation.
Action
Add NoteAdds a new note to a conversation.
Action
Add UserCreate a new user in Support Board.
Action
Delete MessageDeletes an existing message.
Action
Delete NoteDeletes a note from a conversation.
Action
Delete UserDeletes a user and all linked conversations and messages.
Action
Delete UsersDeletes multiple users and all linked conversations and messages.
Action
Direct MessageSends a direct chat message.
Action
Get Agents in ConversationReturns an array with all the agents with at least one message in the conversation.
Action
Get ConversationReturns a conversation and the messages of the conversation.
Action
Get ConversationsReturns all the conversations. Each conversation includes the last message of the conversation.
Action
Get External SettingReturns an external setting. External settings are saved on a dedicated database row.
Action
Get Last Agent in ConversationReturns the last agent who answered a conversation.
Action
Get Last MessageReturns the last message in a conversation.
Action
Get Multi SettingReturns a subsetting of another setting.
Action
Get New ConversationsReturns the conversations created after the given date/ID or with a message created after the given date/ID. Each conversation includes the last message of the conversation.
Action
Get New MessagesReturns the messages of a conversation created after the given date/ID.
Action
Get New User ConversationsReturns the user conversations created after the given date/ID or with a message created after the given date/ID. Each conversation includes the last message of the conversation.
Action
Get NotesReturns the internal notes of a conversation.
Action
Get SettingReturns a setting saved in the Settings area.
Action
Get SettingsReturns an array with all the settings.
Action
Get UserReturns one user's details (name, email, type, extra details) by user ID via api.php function=get-user; returns false when the user does not exist.
Action
Get User ConversationsReturns the conversations of a user. Each conversation includes the last message of the conversation.
Action
Google TranslateTranslates multiple strings via Google Translate.
Action
LoginLogins a user or agent. A user can log in in two ways: via email and password, or via user ID and token. The last value of the response is the encrypted login data ready to be stored in the sb-login cookie. Use the function SBF.loginCookie(response[1]); to store it. Returns false if login is unsuccessful.
Action
Push NotificationSends a Push notification to an agent, a group of agents, or all agents. Push notifications must be enabled in the settings area.
Action
Search ConversationsReturns the conversations matching the search.
Action
Search User ConversationsReturns the conversations of the given user ID that matches the search terms.
Action
Send MessageAdds a new message to an existing conversation.
Action
Telegram Send MessageSends a message to Telegram.
Action
Update Conversation AgentAssigns or update the agent assigned to a conversation.
Action
Update Conversation DepartmentUpdates the department of a conversation.
Action
Update Conversation StatusUpdates the status code of a conversation.
Action
Update MessageUpdates an existing message.
Action
Update UserUpdates the details of an existing user.
Action
WhatsApp Send MessageSends a message to a WhatsApp number.
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 Support Board
HubSpot to Support BoardHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Support BoardSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Support BoardSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Support BoardGoogle Sheets
Gmail to Support BoardGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Support BoardGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Sorry and Support Board, 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 Support Board when something happens in Sorry?
Any of Support Board's 36 actions, including Send Message, Update Conversation Agent, Update Conversation Department and Update Conversation Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Support Board to Sorry?
Support Board has no triggers in the catalog today, so automations start in Sorry. If you need the other direction, ask: your agent reads Support Board's API documentation and adds it.
Do I have to build a connector for Sorry or Support Board?
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 Support Board 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.