Integration
Connect Chaport to ProxiedMail
When something happens in Chaport, your agent does the next thing in ProxiedMail. 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 Chaport and ProxiedMail 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)Chaport holds the live chat conversations and visitor records; ProxiedMail holds the proxy addresses that forward mail to your real inboxes. Connecting them lets a chat event in Chaport look up or change the right proxy email in ProxiedMail, so the forwarding address, description and callback URL match the visitor you just spoke to.
Example flows
What Chaport can start in ProxiedMail
When Chat Closed (instant) in Chaport
then List proxy emails in ProxiedMail
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 Chaport and ProxiedMail
Triggers and actions 8 triggers · 14 actions
- Chat Closed (instant)
Fires when a chat is closed. Webhook event: chat.closed.
- Chat Finished
Triggers when chat is finished.
- Chat Stage Updated (instant)
Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
- Message Read (instant)
Fires when a message is read. Webhook event: message.read.
- New Chat Started
Triggers when chat is started.
- New Message Sent (instant)
Fires when a new message is sent in a chat. Webhook event: message.sent.
- New Visitor (instant)
Fires when a new visitor is created. Webhook event: visitor.created.
- Visitor Updated
Triggers when visitor data is updated.
- Create an Operator
Adds a new operator to your Chaport account and returns the created operator.
- Delete a Message
Deletes one message from a Chaport chat. Identify the visitor and the message you want removed.
- Delete an Operator
Removes an operator from your Chaport account.
- List Operators
Returns every operator in your Chaport account, with each operator's name, email, role and status.
- List Visitors
Returns the visitors in your Chaport account, one page at a time.
- Retrieve an Operator
Returns one Chaport operator with their name, email, role, job title and current status.
- Retrieve a Visitor
Returns one Chaport visitor with their name, contact details, notes and any custom data held about them.
- Retrieve Last Visitor Chat
Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
- Send a Message
Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
- Update an Operator
Updates a Chaport operator's details. Anything you leave blank keeps its current value.
- Update a Visitor
Updates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
- Update Operator Status
Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
- List proxy emails
Lists all proxy email addresses on the ProxiedMail account.
- Update proxy email
Updates an existing ProxiedMail proxy email: its address, the real addresses it forwards to, browsability, description and callback URL.
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 Chaport
Chaport to StripeStripe is a payment processing platform for online businesses.
Chaport to keycdn IP Location FinderGet the IP geolocation data through the simple REST API. All the responses are JSON encoded
Chaport to PublicaWith Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...
Chaport to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Chaport to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Chaport to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into ProxiedMail
Google Sheets to ProxiedMailGoogle Sheets
Gmail to ProxiedMailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ProxiedMailGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Chaport and ProxiedMail, answered
Can a ProxiedMail event start something in Chaport?
No, ProxiedMail offers no triggers here, so every scenario begins with a Chaport event such as a new chat, a closed chat, a new visitor or an updated visitor. ProxiedMail takes part through its two actions, listing proxy emails and updating one.
How does the agent find the right proxy email to change?
It lists the proxy emails on your ProxiedMail account and matches one against details pulled from the Chaport visitor record, such as the address on file. The agent tests every scenario, including the case where no matching proxy is found.
What can start an automation from Chaport?
Any of Chaport's 8 triggers in the catalog, including Chat Closed (instant), Chat Stage Updated (instant), New Chat Started and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in ProxiedMail when something happens in Chaport?
Any of ProxiedMail's 2 actions, including List proxy emails and Update proxy email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ProxiedMail to Chaport?
ProxiedMail has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads ProxiedMail's API documentation and adds it.
Do I have to build a connector for Chaport or ProxiedMail?
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.