Integration
Connect Chaport and CONSENSUS
When Chat Stage Updated (instant) fires in Chaport, your agent runs Create Lead in CONSENSUS, or New Lead in CONSENSUS to Send a Message in Chaport. 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 Chaport and CONSENSUS 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 Chaport and CONSENSUS can do together
From Chaport to CONSENSUS
When Chat Stage Updated (instant) in Chaport
then Create Lead in CONSENSUS
From CONSENSUS to Chaport
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 CONSENSUS
Triggers and actions 10 triggers · 27 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.
- Demo Watched
Triggers when a demo you sent from Sales Accelerator is watched again (its view count goes up).
- New Lead
Triggers when a new lead is captured in Consensus, such as a viewer filling out a demo's lead form.
- Create Demo Link
Creates a marketing share link for a demo.
- Create Lead
Creates a lead in Consensus from a contact's name, email and company.
- Create Mail Merge Link
Creates a mail merge link for a demo using your email platform's merge tags.
- Delete Recipient
Deletes a demo recipient and their data by email address.
- Find Leads
Returns leads captured by your demos, optionally filtered by email address or date range.
- Find Recipient
Finds a demo recipient by email address.
- Find Sent Demos
Returns the demos your team has sent to prospects, with their view counts and recipients.
- Get Current User
Returns the Consensus user this connection acts as and their organization.
- Get Demo by Link Hash
Returns the demo that a Consensus share link points to.
- Get Mail Merge Link
Returns one mail merge link.
- List Mail Merge Links
Returns your mail merge links.
- List Mail Merge Platforms
Returns the email platforms you can build mail merge links for.
- Search Demos
Returns the demos whose title matches your search text, with their preview links and owners.
- Send Demo
Sends a demo to a prospect contact and returns the personal share link.
- Update Sent Demo
Updates the company or opportunity on a demo you sent.
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 ChatraceOmnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...
Chaport to keycdn IP Location FinderGet the IP geolocation data through the simple REST API. All the responses are JSON encoded
Chaport to ProxiedMailProxiedMail provides creating email addresses, forwarding and receiving emails with full context.
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.
More into CONSENSUS
ActiveCampaign to CONSENSUSActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CONSENSUSOrganize anything with Airtable, a modern database created for everyone.
Asana to CONSENSUSAsana is a collaborative information manager for workspace.
ClickUp to CONSENSUSClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CONSENSUSBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CONSENSUSCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Chaport and CONSENSUS, 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 CONSENSUS when something happens in Chaport?
Any of CONSENSUS's 15 actions, including Create Demo Link, Create Lead, Create Mail Merge Link and Send Demo. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from CONSENSUS to Chaport?
Yes. When something happens in CONSENSUS, your agent can act in Chaport too. This page covers both directions: CONSENSUS's triggers and Chaport's actions are listed here as well.
Do I have to build a connector for Chaport or CONSENSUS?
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 CONSENSUS 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.