Integration
Connect Readwise to Reach 360
When Any Document Created (Readwise Reader) fires in Readwise, your agent runs Find a User in Reach 360. 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 Reach 360 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 can start in Reach 360
When Any Document Created (Readwise Reader) in Readwise
then Find a User in Reach 360
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 Reach 360
Triggers and actions 11 triggers · 8 actions
- Any Document Created (Readwise Reader)
Triggers when a new Document is created in Reader.
- Document Archived (Readwise Reader)
Triggers when user archive Reader document.
- Document Finished (Readwise Reader)
Triggers when user finishes reading the document in Reader (reaches 99% article done).
- Document Moved to Inbox (Readwise Reader)
Triggers when user moves document to inbox.
- Document Moved to Later (Readwise Reader)
Triggers when user moves Reader document to later section.
- Document Shortlisted (Readwise Reader)
Triggers when user shortlists a document in Reader.
- Document Tags Updated (Readwise Reader)
Triggers when user updates tags in a Reader document.
- Feed Document Created (Readwise Reader)
Triggers when a new (feed) Document is created in Reader.
- Highlight Created (Readwise)
Triggers when a new highlight has been created in Readwise.
- Highlight Tag Created (Readwise)
Triggers when user added a tag to a highlight.
- Non Feed Document Created (Readwise Reader)
Triggers when a new (non feed) Document is created in Reader.
- Add Document (Readwise Reader)
Add Document to Reader
- Create Highlight (Readwise)
Create a new highlight in Readwise.
- Create Invitation
Sends an invitation to a person to join your Reach 360 team, optionally with their name and the groups they should join.
- Find an Invitation
Finds pending Reach 360 invitations for an email address.
- Find a User
Finds a Reach 360 user by email address and returns their profile, role and report links.
- Get learner report
Returns the courses a Reach 360 learner is enrolled in, with status, progress, quiz score, due and completion dates for each.
- Get user
Returns the details of a single Reach 360 user, including email, name, role and last activity time.
- List users
Returns the users in your Reach 360 account, optionally only those with a given email address.
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 Reach 360
HubSpot to Reach 360HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Reach 360Google Sheets
Gmail to Reach 360Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Reach 360Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Readwise and Reach 360, 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 Reach 360 when something happens in Readwise?
Any of Reach 360's 6 actions, including Create Invitation, Find an Invitation, Find a User and Get learner report. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Reach 360 to Readwise?
Reach 360 has no triggers in the catalog today, so automations start in Readwise. If you need the other direction, ask: your agent reads Reach 360's API documentation and adds it.
Do I have to build a connector for Readwise or Reach 360?
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 Reach 360 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.