--- title: "Connect Chaport to mailfloss - APIANT.ai" description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Add batch of emails for verification\" in mailfloss." canonical: "https://apiant.ai/connect/chaport-to-mailfloss" --- # Connect Chaport to mailfloss When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Add batch of emails for verification** in [mailfloss](https://apiant.ai/connections/mailfloss). Describe the whole flow and it is built, tested on every scenario and kept running. Chaport **8** triggers Chaport **12** actions mailfloss **9** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Chaport and mailfloss to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Chaport can start in mailfloss - When **Chat Stage Updated (instant)** in Chaport then **Add batch of emails for verification** in mailfloss - When **New Chat Started** in Chaport then **Add Email** in mailfloss 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 mailfloss ## Triggers and actions 8 triggers · 21 actions - Trigger **Chat Closed (instant)** Fires when a chat is closed. Webhook event: chat.closed. - Trigger **Chat Finished** Triggers when chat is finished. - Trigger **Chat Stage Updated (instant)** Fires when a chat's stage changes. Webhook event: chat.stageUpdated. - Trigger **Message Read (instant)** Fires when a message is read. Webhook event: message.read. - Trigger **New Chat Started** Triggers when chat is started. - Trigger **New Message Sent (instant)** Fires when a new message is sent in a chat. Webhook event: message.sent. - Trigger **New Visitor (instant)** Fires when a new visitor is created. Webhook event: visitor.created. - Trigger **Visitor Updated** Triggers when visitor data is updated. - Action **Create an Operator** Adds a new operator to your Chaport account and returns the created operator. - Action **Delete a Message** Deletes one message from a Chaport chat. Identify the visitor and the message you want removed. - Action **Delete an Operator** Removes an operator from your Chaport account. - Action **List Operators** Returns every operator in your Chaport account, with each operator's name, email, role and status. - Action **List Visitors** Returns the visitors in your Chaport account, one page at a time. - Action **Retrieve an Operator** Returns one Chaport operator with their name, email, role, job title and current status. - Action **Retrieve a Visitor** Returns one Chaport visitor with their name, contact details, notes and any custom data held about them. - Action **Retrieve Last Visitor Chat** Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript. - Action **Send a Message** Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open. - Action **Update an Operator** Updates a Chaport operator's details. Anything you leave blank keeps its current value. - Action **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. - Action **Update Operator Status** Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time. - Action **Add batch of emails for verification** Submits a batch of email addresses to mailfloss for asynchronous verification and returns the job id. - Action **Add data erasure request** Submits a GDPR/CCPA-style erasure request that permanently deletes the given email addresses from your mailfloss account. - Action **Add Email** Submits an email address to mailfloss for verification and returns the deliverability verdict. - Action **Cancel batch verification job** Cancels a running mailfloss batch verification job. Credits already consumed before the cancellation are not refunded. - Action **Get account details** Returns the details of the mailfloss account this connection belongs to. - Action **Get batch verification results** Retrieve the verification results of a finished mailfloss batch verification job. - Action **Get batch verification status** Reads the current progress of a mailfloss batch verification job: its state plus the running counts of imported, processed, passed and failed addresses. An error occurs if the job is not found. - Action **Get verification job** Fetches a verification job by ID, including its status and verdict counts. An error occurs if the job is not found. - Action **List verification jobs** Returns all verification jobs on the account, optionally filtered by source or status. ## Each app on its own - [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport) - [ **mailfloss** Mailfloss is an email verification platform where you can put your bulk email verification on autopilot and...](https://apiant.ai/connections/mailfloss) Reviews ## What our customers say ## More from Chaport - [ **Chaport to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/chaport-to-stripe) - [ **Chaport to Chatrace** Omnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...](https://apiant.ai/connect/chaport-to-chatrace) - [ **Chaport to keycdn IP Location Finder** Get the IP geolocation data through the simple REST API. All the responses are JSON encoded](https://apiant.ai/connect/chaport-to-keycdn-ip-location-finder) - [ **Chaport to ProxiedMail** ProxiedMail provides creating email addresses, forwarding and receiving emails with full context.](https://apiant.ai/connect/chaport-to-proxiedmail) - [ **Chaport to Publica** With Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...](https://apiant.ai/connect/chaport-to-publica) - [ **Chaport to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/chaport-to-hubspot) ## More into mailfloss - [ **HubSpot to mailfloss** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-mailfloss) - [ **Salesforce to mailfloss** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-mailfloss) - [ **Slack to mailfloss** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-mailfloss) - [ **Google Sheets to mailfloss** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-mailfloss) - [ **Gmail to mailfloss** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-mailfloss) - [ **Google Calendar to mailfloss** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-mailfloss) Questions ## Chaport and mailfloss, answered ### ### What can start an automation from Chaport? Any of Chaport's 8 triggers in the catalog, including Chat Stage Updated (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in mailfloss when something happens in Chaport? Any of mailfloss's 9 actions, including Add batch of emails for verification, Add data erasure request, Add Email and Get account details. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from mailfloss to Chaport? mailfloss has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads mailfloss's API documentation and adds it. ### ### Do I have to build a connector for Chaport or mailfloss? 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 Chaport and mailfloss 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.