Integration
Connect NobelSMS and Sorry
When New Contact fires in NobelSMS, your agent runs Update status page in Sorry, or New notice in Sorry to Create Contact in NobelSMS. 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 NobelSMS and Sorry 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 NobelSMS and Sorry can do together
From NobelSMS to Sorry
When New Contact in NobelSMS
then Update status page in Sorry
When New SMS Delivery Record in NobelSMS
then Add component in Sorry
From Sorry to NobelSMS
When New notice in Sorry
then Create Contact in NobelSMS
When New notice in Sorry
then Update Contact in NobelSMS
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 NobelSMS and Sorry
Triggers and actions 3 triggers · 26 actions
Trigger
New ContactTriggers when a new contact is added to your NobelSMS contacts.
Trigger
New SMS Delivery RecordTriggers when a new SMS delivery record (sent or received message with its status) is logged in the last day.
Action
Add Number to Black ListAdds a phone number to your black list so it no longer receives messages.
Action
Create ContactCreates a contact with a phone number and assigns it to one or more tags.
Action
Create TagCreates a tag for grouping contacts or black-list numbers.
Action
Delete ContactDeletes a contact by its ID.
Action
Find ContactsSearches your contacts by phone number, name or tag and returns the matches.
Action
Get BalanceReturns the balance and currency of each of your NobelSMS accounts.
Action
Get ContactReturns one contact by its ID.
Action
Send Bulk SMSSends the same SMS message to several phone numbers in one request and returns sent and rejected counts.
Action
Send Single SMSSends an SMS message from your sender name or number to one or more phone numbers.
Action
Update ContactUpdates a contact's phone, name, tags or comments. Only the fields you fill in are changed.
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.
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 NobelSMS
NobelSMS to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
NobelSMS to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
NobelSMS to StripeStripe is a payment processing platform for online businesses.
NobelSMS to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
NobelSMS to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
NobelSMS to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Sorry
HubSpot to SorryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SorrySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SorrySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SorryGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SorryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SorryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
NobelSMS and Sorry, answered
What can start an automation from NobelSMS?
Any of NobelSMS's 2 triggers in the catalog, including New Contact and New SMS Delivery Record. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sorry when something happens in NobelSMS?
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 NobelSMS?
Yes. When something happens in Sorry, your agent can act in NobelSMS too. This page covers both directions: Sorry's triggers and NobelSMS's actions are listed here as well.
Do I have to build a connector for NobelSMS 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 NobelSMS 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.