Integration
Connect eSputnik and Sorry
When New Contact fires in eSputnik, your agent runs Update status page in Sorry, or New notice in Sorry to Add contact to segment in eSputnik. 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 eSputnik 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)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 eSputnik and Sorry can do together
From eSputnik to Sorry
When New Contact in eSputnik
then Update status page in Sorry
From Sorry to eSputnik
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 eSputnik and Sorry
Triggers and actions 3 triggers · 28 actions
- New Contact
Triggered when a new contact is created in eSputnik, optionally limited to contacts matching the details you enter.
- New Contact in Segment
Triggers when a contact is added to the eSputnik segment you choose.
- Add contact to segment
Adds one or more contacts to a static segment in eSputnik, identified by contact IDs or external customer IDs.
- Add emails to unsubscribed list
Adds one or more email addresses to the eSputnik list of unsubscribed contacts.
- Add/Update Contact
Adds a new contact or updates the existing matching contact, including its channels, address and additional fields, and returns the contact's ID.
- Delete contact
Deletes a contact by its eSputnik contact ID, optionally erasing all of the contact's data permanently.
- Delete contact from segment
Removes one or more contacts from a static segment, identified by their eSputnik contact IDs or external customer IDs.
- Find contacts
Returns up to 500 contacts that match the specified external ID, email address, phone number, first name or last name.
- Get contact
Returns an eSputnik contact by ID, including its channels, address, segments and additional field values. An error occurs if the contact is not found.
- List segments
Returns the contact segments in the eSputnik account, optionally narrowed by name, with each segment's id, name and type.
- Send Email
Sends an email message to one or more recipients. A new contact is created for any address that does not already exist in eSputnik.
- Send Event
Sends a backend event for a contact to eSputnik, where it can start workflows and supply dynamic content for messages.
- Send Viber message
Sends a Viber message to a list of phone numbers or to a segment, and returns the queueing result for each recipient. A new contact is created for a phone number that does not exist yet.
- Subscribe Contact
Subscribes a contact through a double opt-in flow, creating an unconfirmed contact if none exists or updating the existing one, and returns the contact's ID and email subscription status.
- 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.
- Update status page
Updates 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 eSputnik
eSputnik to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
eSputnik to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
eSputnik to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
eSputnik to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
eSputnik to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
eSputnik to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Sorry
Questions
eSputnik and Sorry, answered
What can start an automation from eSputnik?
Any of eSputnik's 2 triggers in the catalog, including New Contact and New Contact in Segment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sorry when something happens in eSputnik?
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 eSputnik?
Yes. When something happens in Sorry, your agent can act in eSputnik too. This page covers both directions: Sorry's triggers and eSputnik's actions are listed here as well.
Do I have to build a connector for eSputnik 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 eSputnik 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.