---
title: "Connect Chaport to Pylon - APIANT.ai"
description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Add internal note to issue\" in Pylon."
canonical: "https://apiant.ai/connect/chaport-to-pylon"
---

# Connect Chaport to Pylon

When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Add internal note to issue** in [Pylon](https://apiant.ai/connections/pylon). Describe the whole flow and it is built, tested on every scenario and kept running.

Chaport **8** triggers Chaport **12** actions Pylon **25** 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 Pylon 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 Pylon

- When **Chat Stage Updated (instant)** in Chaport then **Add internal note to issue** in Pylon
- When **New Chat Started** in Chaport then **Add task** in Pylon

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 Pylon

## Triggers and actions 8 triggers · 37 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 internal note to issue**

Adds an internal note to a Pylon issue. Internal notes are not visible to the requester.

- Action

**Add tag**

Creates a new tag in Pylon that can be applied to accounts, articles or issues.

- Action

**Add task**

Creates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.

- Action

**Create Account**

Creates a new customer account in Pylon with its name, domains, owner, tags and other details.

- Action

**Create Account Activity**

Creates a custom activity on a Pylon account's timeline.

- Action

**Create Call Recording**

Creates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.

- Action

**Delete account**

Permanently deletes a Pylon account by its ID or external ID.

- Action

**Delete issue**

Permanently deletes an issue in Pylon.

- Action

**Find Account by Name**

Finds Pylon accounts by name, by exact or partial match, returning the matching accounts.

- Action

**Find contacts by criteria**

Returns the contacts that match the specified search text and/or filter.

- Action

**Find issues by criteria**

Returns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.

- Action

**Get account**

Returns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.

- Action

**Get contact**

Returns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.

- Action

**Get issue**

Returns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.

- Action

**Get user**

Returns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.

- Action

**Get Users**

Returns the users in your Pylon organization, optionally including deactivated users.

- Action

**List accounts**

Returns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.

- Action

**List contacts**

Returns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.

- Action

**List tags**

Returns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.

- Action

**List teams**

Returns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.

- Action

**Reply to issue**

Sends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.

- Action

**Update Account**

Updates an existing Pylon account. Only the fields you fill in are changed.

- Action

**Update contact**

Updates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.

- Action

**Update issue**

Updates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.

- Action

**Update Issue Followers**

Adds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.

## Each app on its own

- [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport)
- [ **Pylon** Pylon is a modern, powerful support system built for B2B.](https://apiant.ai/connections/pylon)

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 Pylon

- [ **HubSpot to Pylon** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-pylon)
- [ **Salesforce to Pylon** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-pylon)
- [ **Slack to Pylon** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-pylon)
- [ **Google Sheets to Pylon** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-pylon)
- [ **Gmail to Pylon** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-pylon)
- [ **Google Calendar to Pylon** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-pylon)

Questions

## Chaport and Pylon, 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 Pylon when something happens in Chaport?

Any of Pylon's 25 actions, including Create Account, Create Account Activity, Create Call Recording and Update Account. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Pylon to Chaport?

Pylon has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it.

###

### Do I have to build a connector for Chaport or Pylon?

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 Pylon 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.
