Integration
Connect Sorry to Emelia
When New notice fires in Sorry, your agent runs Add Contact to a Campaign in Emelia. 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 Emelia 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 Emelia
When New notice in Sorry
then Add Contact to a Campaign in Emelia
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 Emelia
Triggers and actions 1 trigger · 31 actions
- New notice
Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.
- Add component
Creates a new component on a Sorry status page, optionally nested under a parent component.
- Add notice
Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.
- Add notice update
Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.
- Add subscriber
Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.
- Delete notice
Deletes a notice (incident, maintenance or general) from a Sorry status page.
- Delete subscriber
Permanently removes a subscriber from a status page.
- Get notice
Returns a single notice from a status page, including its type, state, subject, synopsis and link.
- 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.
- List components
Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.
- 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.
- List notice updates
Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.
- List status pages
Returns all status pages in your Sorry account, optionally filtered by name or creation date.
- List subscribers
Returns the subscribers on a status page, optionally only those who receive notices for a specific component.
- Update component
Updates a component on a Sorry status page, such as its name, description, position or parent component.
- 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.
- Add campaign
Creates a new email campaign in Emelia with the given name and time zone.
- Add Contact to a Campaign
Adds a contact to an Emelia campaign.
- Add Contact to a List
Adds a single contact to an Emelia list (and to any campaigns using that list), optionally updating it if it already exists.
- Add Contact to Blacklist
Adds an email address or an entire domain to your Emelia blacklist so it is never contacted by your campaigns.
- Add list
Creates a new, empty contact list in Emelia.
- Delete contact
Deletes a contact (and its company data) from an Emelia contact list; the removal also propagates to campaigns using that list.
- Get campaign
Returns the full configuration of an Emelia campaign, including the contact lists attached to it and excluded from it.
- Get campaign statistics
Returns sending, open, click and reply statistics for an Emelia campaign, overall and per step.
- Get contact
Returns a single contact from an Emelia contact list.
- List Campaign Contacts
Returns the contacts enrolled in an email campaign, optionally filtered by an engagement event or a search term.
- List campaigns
Returns all campaigns in your Emelia account.
- List contacts
Returns the contacts in an Emelia contact list, optionally filtered by search text or an exact email or LinkedIn URL.
- Search Contact
Searches a contact list for contacts by exact email, LinkedIn URL, or free text, and returns the matches.
- Set a Custom Field to a Contact
Sets the value of a custom field on a contact in an Emelia campaign, identified by email or LinkedIn profile URL.
- Test Webhook
Sends a test call to an existing Emelia webhook.
- Update contact
Updates an Emelia contact's values; fields you don't send stay unchanged, and changes propagate to campaigns using the contact's list.
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 Emelia
Benetics to EmeliaBenetics is a construction efficiency platform built in the cloud.
HubSpot to EmeliaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to EmeliaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to EmeliaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to EmeliaGoogle Sheets
Gmail to EmeliaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Sorry and Emelia, 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 Emelia when something happens in Sorry?
Any of Emelia's 16 actions, including Update contact, Add campaign, Add Contact to a Campaign and Add Contact to a List. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Emelia to Sorry?
Emelia has no triggers in the catalog today, so automations start in Sorry. If you need the other direction, ask: your agent reads Emelia's API documentation and adds it.
Do I have to build a connector for Sorry or Emelia?
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 Emelia 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.