Integration
Connect Emma and eSputnik
When New mailing fires in Emma, your agent runs Add contact to segment in eSputnik, or New Contact in eSputnik to Get member by email in Emma. 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 Emma and eSputnik 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 Emma and eSputnik can do together
From Emma to eSputnik
When New mailing in Emma
then Add contact to segment in eSputnik
When New subscriber in Emma
then Add emails to unsubscribed list in eSputnik
From eSputnik to Emma
When New Contact in eSputnik
then Get member by email in Emma
When New Contact in Segment in eSputnik
then Opt out member in Emma
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 Emma and eSputnik
Triggers and actions 4 triggers · 27 actions
Trigger
New mailingPolling trigger: fires when a new mailing (campaign) is created in the account.
Trigger
New subscriberPolling trigger: fires when a new subscriber (member) is added to the account.
Action
Delete memberDelete a member by member ID (sets status to deleted).
Action
Get mailingGet a single mailing by mailing ID.
Action
Get mailing membersGet the members a mailing was sent to.
Action
Get memberGet a single member by member ID.
Action
Get member by emailLook up a single member by email address.
Action
List fieldsList the member data fields defined in the account.
Action
List groupsList all member groups in the account.
Action
List mailingsList mailings (campaigns) in the account.
Action
List membersList all members (subscribers) in the Emma account.
Action
List members in groupList the members belonging to a specific group.
Action
List signup formsList the signup forms in the account.
Action
Opt out memberOpt a member out of all mailings by email address.
Trigger
New ContactTriggered when a new contact is created in eSputnik, optionally limited to contacts matching the details you enter.
Trigger
New Contact in SegmentTriggers when a contact is added to the eSputnik segment you choose.
Action
Add contact to segmentAdds one or more contacts to a static segment in eSputnik, identified by contact IDs or external customer IDs.
Action
Add emails to unsubscribed listAdds one or more email addresses to the eSputnik list of unsubscribed contacts.
Action
Add ordersAdds or updates up to 1000 orders in eSputnik, each linked to a contact, and fails if any order is rejected.
Action
Add/Update ContactAdds a new contact or updates the existing matching contact, including its channels, address and additional fields, and returns the contact's ID.
Action
Delete contactDeletes a contact by its eSputnik contact ID, optionally erasing all of the contact's data permanently.
Action
Delete contact from segmentRemoves one or more contacts from a static segment, identified by their eSputnik contact IDs or external customer IDs.
Action
Find contactsReturns up to 500 contacts that match the specified external ID, email address, phone number, first name or last name.
Action
Get contactReturns an eSputnik contact by ID, including its channels, address, segments and additional field values. An error occurs if the contact is not found.
Action
List segmentsReturns the contact segments in the eSputnik account, optionally narrowed by name, with each segment's id, name and type.
Action
Send EmailSends an email message to one or more recipients. A new contact is created for any address that does not already exist in eSputnik.
Action
Send EventSends a backend event for a contact to eSputnik, where it can start workflows and supply dynamic content for messages.
Action
Send SMSSends an SMS message to a list of phone numbers or to a segment. Returns the queueing result and message ID for each recipient.
Action
Send Viber messageSends 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.
Action
Subscribe ContactSubscribes 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.
Action
Update contactUpdates an existing eSputnik contact's details, channels, address and additional fields by contact ID. Updating a deleted contact restores it.
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 Emma
Emma to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Emma to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Emma to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Emma to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Emma to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Emma to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into eSputnik
ActiveCampaign to eSputnikActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to eSputnikOrganize anything with Airtable, a modern database created for everyone.
Asana to eSputnikAsana is a collaborative information manager for workspace.
ClickUp to eSputnikClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to eSputnikDiscord is an all-in-one voice and text chat for gamers.
Brevo to eSputnikBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Emma and eSputnik, answered
What can start an automation from Emma?
Any of Emma's 2 triggers in the catalog, including New mailing and New subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in eSputnik when something happens in Emma?
Any of eSputnik's 15 actions, including Send Email, Send Event, Send SMS and Send Viber message. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from eSputnik to Emma?
Yes. When something happens in eSputnik, your agent can act in Emma too. This page covers both directions: eSputnik's triggers and Emma's actions are listed here as well.
Do I have to build a connector for Emma or eSputnik?
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 Emma and eSputnik 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.