Sync your highlights from Readwise into Tana.
Readwise integration with Tana is available for those with a Readwise subscription or if you started their free trial which allows for export of 10 most recently highlighted documents.
For more on what Readwise is, check out their webpage: https://readwise.io/
Before you begin, you must read the following important information about this integration:
Log into your Readwise account and go into Tana as Export option or head over to this page for the Tana Export settings: https://readwise.io/export/tana/preferences
It will prompt you to create a Tana API and to paste it into Readwise. Do this by going to your Settings > API tokens, then pick the workspace you want them synced to, and hit Create.
A token is immediately created and copied to your clipboard. Head back to Readwise and plug that into the setup and hit Save.
This is an overview of all the options available on the Tana Export page:
We know Tanarians care a lot about how incoming information is structured when it comes from elsewhere! Below are instructions on how to responsibly tweak your export settings without making a huge mess in the process that will need a lot of cleanup.
1. When fine tuning your settings, turn on the following settings, and the rest keep off:
2. For your first export, pick a few documents to export at the time to see what they look like in Tana: Pick ones with many different features used, like document tags and notes, highlight tags and notes and images, books and videos, etc. so you're testing every possibility you're likely to see in your highlights.
4. Find the exported node and take a look: Look in Library, or try to @-mention a node called "Readwise". Reminder that upon initial export, Readwise will create supertags and fields in your workspace, saving them in the Schema. From this initial export, you may want to change some things in the export settings, and try again. Hard-delete (Cmd/Ctrl+Shift+Backspace) the document nodes in Tana before re-exporting. Do NOT delete the main Readwise node.
5. Tweak export settings: Make adjustments in Readwise based on what you saw.
6. To make a fresh export of a document after making adjustments: You must tell Readwise to "refresh" a document which will reset Readwise's memory of having synced that particular document before. (This essentially makes Readwise forget the nodeID associated with this document)
7. Repeat steps 3 to 6 until you're happy!
8. Once you're satisfied, feel free to turn "Export Automatically" ON and "Select items to be exported" OFF. This will make Readwise sync everything in the next sync cycle, and every other document and highlight that gets added thereafter. If you have many highlights, this may take some time and occasionally freeze Tana. The work happens in the background, so it's safe to close it or leave it open while it's doing a big sync.
Properly making the supertags: You can promote the fields to the supertags, rearrange them anyway you see fit, pick a colour, and even add fields of your own.
Ideas for surfacing your Readwise content: By default, Readwise will sync to a special Readwise node in the Library. Below is some inspiration on how you can surface this content:
If you have previous imports to Tana from Readwise, either through Reader Export via clipboard or other custom implementation from our very inventive community such as Brandon's readwise.toolsfortana, you may be wondering whether to merge your existing information with the new setup, or not.
The following section will be important to read for your considerations.
Readwise does not retrieve any information from your workspace, other than the nodes, tags and fields that it creates and saves the nodeID from. For the first iteration of this integration we've decided to only permit Write permissions and limit Read permissions. From a security perspective it's good because it means that Readwise has no access to your workspace content other than the nodes it creates. From an automation perspective it may leave a bit to desire because your imports will not automatically link to nodes that exist in your workspace. That said...
Tana AI and commands can fill a lot of last mile connections: A workaround is to use AI to connect plain text with nodes in your graph once the content is there.
It's currently not possible to create multiple nodes inside of a field: This means that a highlight Tag field for instance will export tags as just words in a single node. However, if you use AI in Tana, this info can be extracted (see point above).
Merge direction is super important: When merging your tag/field/node with a Readwise-equivalent object, always merge in the direction of what Readwise had created. This ensures that the Readwise-synced nodeID is preserved so it can send updates to it in the future.
Above is important because deleted nodes still get synced to: If you delete a document node that Readwise creates, Readwise will continue to push changes to it because it looks for a nodeID match, no matter where it is in the graph. See Step 3 on how to properly disassociate document nodes created by Readwise.
For a full reset, make a new API token: Replacing the API token with a new one will prompt a fresh export, no matter what was exported to your workspace in the past. Readwise relinquishes all previous nodeIDs it has saved, and all new tags, fields and nodes will be created. Useful if you want to do something like change which workspace it gets synced to, or start from scratch.