Integration
Connect Chaport to Aurora Inbox
When something happens in Chaport, your agent does the next thing in Aurora Inbox. 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 Aurora Inbox 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 Chaport can start in Aurora Inbox
When Chat Stage Updated (instant) in Chaport
then Add chat in Aurora Inbox
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 Aurora Inbox
Triggers and actions 8 triggers · 32 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.
- Add chat
Creates a new chat conversation for a contact on a specific channel.
- Add company
Adds a new company.
- Add tag
Creates a tag in Aurora Inbox that can be attached to any chat. If a tag with the same name already exists, that tag is returned.
- Create Opportunity
Create a new opportunity
- Delete contact
Deletes a contact by its ID.
- Find chats by criteria
Returns up to 25 chats that match the specified search term, channel, team, unanswered and unread criteria.
- Get Chat
Returns one chat by id: contact, channel, channel type, owner, agents and status flags.
- Get company
Fetches a single company by id.
- Get contact
Fetches a single contact by id.
- Get or Create Contact
Finds a contact by phone number, or creates one when no contact has that number. When a contact is found, any name, email, company name and custom property values you supply are applied to it.
- List Chat Opportunities
Returns the opportunities (deals) attached to a chat.
- List Chat Tags
Returns all tags currently attached to a chat: attachment id, roomId, tagId, tagName.
- List companies
Lists companies in Aurora Inbox, optionally filtered by a keyword search.
- List tags
Returns all tags configured in the Aurora Inbox account, optionally with the number of chats tagged with each.
- List teams
Returns all teams configured in the Aurora Inbox account, including their members and roles.
- Send media message
Sends a file (image, video, audio or document) to an Aurora Inbox chat, with an optional caption.
- Send message
Sends a text message, or an internal note visible only to agents, to an Aurora Inbox chat.
- Tag chat
Attaches a tag to a chat, either an existing tag or one looked up by name (created if no tag with that name exists). If the chat already has the tag, the existing attachment is returned.
- Update company
Updates fields on an existing company.
- Update Contact
Updates an existing contact's name, phone, email, company name and custom property values. Blank fields keep their current values.
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 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.
Chaport to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
More into Aurora Inbox
Slack to Aurora InboxSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Aurora InboxGoogle Sheets
Gmail to Aurora InboxGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Aurora InboxGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Chaport and Aurora Inbox, 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 Aurora Inbox when something happens in Chaport?
Any of Aurora Inbox's 20 actions, including Create Opportunity, Send media message, Send message and Update company. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Aurora Inbox to Chaport?
Aurora Inbox has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads Aurora Inbox's API documentation and adds it.
Do I have to build a connector for Chaport or Aurora Inbox?
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.