Readwise can send your saved highlights and notes into a specific client, company, or personal mind. Armbrain checks for changes in the background, keeps the Readwise source link, and updates a book when its highlights change. Prospect minds are intentionally excluded from automatic connector ingest.
Before you start
You need:
- A Readwise account with highlights to import.
- The client, company, or personal mind where those highlights belong.
- Your personal Readwise access token from readwise.io/access_token.
Treat the token like a password. Armbrain validates it with Readwise, encrypts it before storage, and never displays it again.
Connect from Armbrain HQ
- Open Connectors in Armbrain HQ.
- Choose Readwise.
- Select the client, company, or personal mind that should receive the highlights.
- Paste your Readwise access token.
- Select Connect.
Only owners and editors of that mind can add its Readwise connection.
Connect while chatting with Armbrain
Tell Armbrain which client you are working on, then say:
Connect Readwise to this mind.
Armbrain returns a short-lived, single-use Armbrain HQ setup link for that mind. Open the link and paste the token into HQ. Do not paste the token into chat. The same owner/editor permission check applies, and the setup link cannot be reused or moved to another mind.
What happens after connection
- Each Readwise book or article becomes a source with its highlights, notes, author, tags, and source links.
- Deleted books and books with no active highlights retire their current Armbrain memories. Deleted or discarded individual highlights disappear from the next version while the remaining highlights stay current.
- Content changes and deletions are serialized per book in the database. A delayed older update cannot restore content after a newer deletion, and repeating the same event is safe.
- Large libraries sync in bounded batches and resume automatically. Each discovery result is hard-capped at 100 books and 512 KiB of queued payload. If Armbrain stops inside one provider page, it remembers durable book-state references rather than a fragile numeric offset, so reordering within that resumed page does not duplicate completed items.
- Later polls request only changes since the last completed sync window.
- Readwise tokens do not reveal a stable provider account identity. To change accounts or replace an expired token, remove the old connector in HQ and connect again. The new connection gets a separate generation so two accounts cannot mix source state; previously ingested history is not rewritten.
Verify the connection
Open Connectors in Armbrain HQ and confirm that Readwise is active for the intended mind. After the first sync, search that mind for a distinctive phrase from one of your highlights and check that the result links back to Readwise.
If initial setup reports that the token is invalid, create or copy a fresh token from Readwise and try the setup form again. If an existing connection needs a new token, remove it and create a new connection. If Readwise is temporarily rate-limiting requests, wait a few minutes and retry.