Integration
Connect Mailosaur to SupportBee
When something happens in Mailosaur, your agent does the next thing in SupportBee. Describe it 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 Mailosaur and SupportBee to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Mailosaur can start in SupportBee
When New message in Mailosaur
then Add comment in SupportBee
When New message in Mailosaur
then Add reply in SupportBee
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 Mailosaur and SupportBee
Triggers and actions 1 trigger · 22 actions
Trigger
New messageFires when a new email/SMS arrives in a server.
Action
Add serverCreate a server (inbox).
Action
Delete messageDelete a message.
Action
Delete serverDelete a server.
Action
Find messages by criteriaSearch messages by sentFrom/sentTo/subject/body.
Action
Get messageRetrieve one email/SMS message.
Action
Get serverRetrieve a server.
Action
List messagesList messages in a server.
Action
List serversList servers (inboxes).
Action
Send emailSend an email.
Action
Update serverUpdate a server.
Action
Add commentAdds a private (agent-only) comment to a SupportBee ticket.
Action
Add replyPosts a reply to a SupportBee ticket. Admin users can reply on behalf of another agent.
Action
Archive ticketArchives an unarchived SupportBee ticket.
Action
Create TicketCreates a New Ticket in your SupportBee account.
Action
Delete ticketPermanently deletes a trashed SupportBee ticket. Only admins can delete tickets, and the ticket must be in the trash first.
Action
Find tickets by queryReturns up to 15 tickets, most recent activity first, that match the search keywords.
Action
Get ticketRetrieves a single SupportBee ticket by its id.
Action
List commentsLists all the comments on a SupportBee ticket.
Action
List repliesLists all replies on a SupportBee ticket.
Action
List ticketsReturns the tickets in your SupportBee desk, most recently active first, optionally narrowed by status, assignee, label, requester or activity date.
Action
Trash ticketMoves a ticket to the trash. A trashed ticket can then be deleted permanently with Delete ticket.
Action
Update ticket assignmentAssigns a SupportBee ticket to an agent. If the ticket is already assigned to a team, the agent must be a member of that team.
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 Mailosaur
Mailosaur to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mailosaur to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailosaur to StripeStripe is a payment processing platform for online businesses.
Mailosaur to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mailosaur to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Mailosaur to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into SupportBee
HubSpot to SupportBeeHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SupportBeeSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SupportBeeSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SupportBeeGoogle Sheets
Gmail to SupportBeeGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SupportBeeGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Mailosaur and SupportBee, answered
What can start an automation from Mailosaur?
Any of Mailosaur's 1 trigger in the catalog, including New message. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SupportBee when something happens in Mailosaur?
Any of SupportBee's 12 actions, including Create Ticket, Update ticket assignment, Add comment and Add reply. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SupportBee to Mailosaur?
SupportBee has no triggers in the catalog today, so automations start in Mailosaur. If you need the other direction, ask: your agent reads SupportBee's API documentation and adds it.
Do I have to build a connector for Mailosaur or SupportBee?
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.
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.