Integration
Connect MailUp to Mercury
When New Email Message in List fires in MailUp, your agent runs Add customer in Mercury. 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 MailUp and Mercury 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 MailUp can start in Mercury
When New Email Message in List in MailUp
then Add customer in Mercury
When New Group in MailUp
then Get invoice in Mercury
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 MailUp and Mercury
Triggers and actions 4 triggers · 42 actions
Trigger
New Email Message in ListA new email message was created in the list. MailUp is a multi-list environment and messages are list-specific.
Trigger
New GroupNew group added to the specified list. MailUp is a multi-list environment and groups are list-specific.
Trigger
New Recipient SubscribedThere is a new subscriber in the specified list. MailUp is a multi-list environment.
Trigger
New Recipient UnsubscribedA recipient unsubscribed from the specified list. MailUp is a multi-list environment.
Action
Add listCreate a new list. POST Console/List
Action
Add Recipient to GroupAdd recipient to the specified group on the list.
Action
Add Recipient to ListAdds a new recipient to the specified list as a subscriber.
Action
Create New Email MessageCreate a new email message on the specified list.
Action
Create New GroupAdd a new group to the specified list. MailUp is a multi-list environment.
Action
Delete email messageDelete an email message. DELETE Console/List/{id_List}/Email/{id_Message}
Action
Delete groupDelete a group in a list. DELETE Console/List/{id_List}/Group/{id_Group}
Action
Delete listDelete a list. DELETE Console/List/{id_List}
Action
Get email messageRetrieve email message details. GET Console/List/{id_List}/Email/{id_Message}
Action
Get listRetrieve list details by id. GET Console/List/{id_List}
Action
List email messagesRetrieve email messages of a list. GET Console/List/{id_List}/Emails
Action
List Email Message Sendingslists the sendings (send tasks, with recipients count and status) created for an email message.
Action
List Group RecipientsLists the recipients in a MailUp group (GET Console/Group/{id_group}/Recipients), with id, email, name and personal data fields.
Action
List groupsRetrieve groups of a list. GET Console/List/{id_List}/Groups
Action
List listsRetrieve the console's lists. GET Console/List on services.mailup.com/API/v1.1/Rest/ConsoleService.svc
Action
List subscribed recipientsRetrieve subscribed recipients of a list. GET Console/List/{id_List}/Recipients/Subscribed
Action
Remove recipient from groupUnsubscribe a recipient from a group. DELETE Console/Group/{id_Group}/Unsubscribe/{id_Recipient}
Action
Remove Recipient From ListThis method unsubscribe the given recipient from the specified list.
Action
Send Message to Email AddressSends the specified message (previously created in MailUp in the specified List) to the email address specified.
Action
Send Message to GroupSend a message to a predefined group in the specified list.
Action
Send message to listSend an email message to all recipients of a list. POST Console/List/{id_List}/Email/{id_Message}/Send
Action
Unsubscribe recipient from listUnsubscribe a recipient from a list. DELETE Console/List/{id_List}/Unsubscribe/{id_Recipient}
Action
Update email messageModify an email message. PUT Console/List/{id_List}/Email/{id_Message}
Action
Update groupModify a group in a list. PUT Console/List/{id_List}/Group/{id_Group}
Action
Update listModify details of a list. PUT Console/List/{id_List}
Action
Add customerCreates a new Accounts Receivable customer in Mercury that you can invoice.
Action
Add internal transferTransfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
Action
Add recipientCreates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
Action
Get invoiceReturns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
Action
Get organizationReturns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
Action
Get recipientReturns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
Action
Get transactionReturns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
Action
List accountsReturns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
Action
List account statementsReturns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
Action
List categoriesReturns the organization's custom expense categories used to classify transactions.
Action
List customersReturns the accounts receivable customers on your Mercury account (up to 1000).
Action
List invoicesReturns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
Action
List recipientsReturns the payment recipients saved in your Mercury account (up to 1000).
Action
List transactionsReturns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
Action
Send moneySends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
Action
Update recipientUpdates an existing payment recipient's name, contact details and payment routing information.
Action
Update transactionUpdates the note and/or category of an existing Mercury transaction.
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 MailUp
MailUp to SendPulseSendPulse is an Integrated messaging platform providing user communication on all devices with Emails, SMS...
MailUp to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MailUp to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MailUp to StripeStripe is a payment processing platform for online businesses.
MailUp to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MailUp to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Mercury
HubSpot to MercuryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to MercurySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to MercurySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to MercuryGoogle Sheets
Gmail to MercuryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MercuryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
MailUp and Mercury, answered
What can start an automation from MailUp?
Any of MailUp's 4 triggers in the catalog, including New Email Message in List, New Group, New Recipient Subscribed and New Recipient Unsubscribed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mercury when something happens in MailUp?
Any of Mercury's 17 actions, including Send money, Update recipient, Update transaction and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mercury to MailUp?
Mercury has no triggers in the catalog today, so automations start in MailUp. If you need the other direction, ask: your agent reads Mercury's API documentation and adds it.
Do I have to build a connector for MailUp or Mercury?
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 MailUp and Mercury 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.