Integration
Connect Readwise and Chaport
When Any Document Created (Readwise Reader) fires in Readwise, your agent runs Send a Message in Chaport, or Chat Stage Updated (instant) in Chaport to Add Document (Readwise Reader) in Readwise. 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 Readwise and Chaport 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 Readwise and Chaport can do together
From Readwise to Chaport
When Any Document Created (Readwise Reader) in Readwise
then Send a Message in Chaport
When Document Moved to Inbox (Readwise Reader) in Readwise
then Create an Operator in Chaport
From Chaport to Readwise
When Chat Stage Updated (instant) in Chaport
then Add Document (Readwise Reader) in Readwise
When New Chat Started in Chaport
then Create Highlight (Readwise) in Readwise
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 Readwise and Chaport
Triggers and actions 19 triggers · 14 actions
Trigger
Any Document Created (Readwise Reader)Triggers when a new Document is created in Reader.
Trigger
Document Archived (Readwise Reader)Triggers when user archive Reader document.
Trigger
Document Finished (Readwise Reader)Triggers when user finishes reading the document in Reader (reaches 99% article done).
Trigger
Document Moved to Inbox (Readwise Reader)Triggers when user moves document to inbox.
Trigger
Document Moved to Later (Readwise Reader)Triggers when user moves Reader document to later section.
Trigger
Document Shortlisted (Readwise Reader)Triggers when user shortlists a document in Reader.
Trigger
Document Tags Updated (Readwise Reader)Triggers when user updates tags in a Reader document.
Trigger
Feed Document Created (Readwise Reader)Triggers when a new (feed) Document is created in Reader.
Trigger
Highlight Created (Readwise)Triggers when a new highlight has been created in Readwise.
Trigger
Highlight Tag Created (Readwise)Triggers when user added a tag to a highlight.
Trigger
Non Feed Document Created (Readwise Reader)Triggers when a new (non feed) Document is created in Reader.
Action
Add Document (Readwise Reader)Add Document to Reader
Action
Create Highlight (Readwise)Create a new highlight in Readwise.
Trigger
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers 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 StartedTriggers 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 UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates 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 StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
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 Readwise
Readwise to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Readwise to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Readwise to StripeStripe is a payment processing platform for online businesses.
Readwise to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Readwise to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Readwise to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
More into Chaport
aikstockdata to ChaportKOSPI/KOSDAQ/KONEX daily settled closes, DART filings with receipt times, quarterly earnings
ActiveCampaign to ChaportActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to ChaportOrganize anything with Airtable, a modern database created for everyone.
Asana to ChaportAsana is a collaborative information manager for workspace.
Freshdesk to ChaportFreshdesk is a cloud-based customer support and helpdesk platform.
Brevo to ChaportBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Readwise and Chaport, answered
What can start an automation from Readwise?
Any of Readwise's 11 triggers in the catalog, including Any Document Created (Readwise Reader), Document Moved to Inbox (Readwise Reader), Document Moved to Later (Readwise Reader) and Document Tags Updated (Readwise Reader). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Chaport when something happens in Readwise?
Any of Chaport's 12 actions, including Create an Operator, Send a Message, Update an Operator and Update a Visitor. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Chaport to Readwise?
Yes. When something happens in Chaport, your agent can act in Readwise too. This page covers both directions: Chaport's triggers and Readwise's actions are listed here as well.
Do I have to build a connector for Readwise or Chaport?
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 Readwise and Chaport 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.