Connect Readwise and Reader

≈ 1 min Extension Bearer Token

Before you start

• A Readwise account (Reader is included).
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Readwise / Reader

Set it up

1. Copy the token at readwise.io/access_token.

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Readwise / Reader in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Readwise / Reader Under Integration App / Service, pick Readwise / Reader. There is no Auth Type menu: Readwise / Reader uses a Bearer Token.
   2. 2 Step 2:Name it For example Readwise – me. A Description is optional.
   3. 3 Step 3:Paste the token Paste the token into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Readwise / Reader; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Reader (Articles) › Save document with a web address: it appears in your Reader inbox.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to readwise.io. AWFlow’s servers never relay the call.

Privacy & your data →

Common issues

• “401 … the access token was rejected”. Copy the token again from readwise.io/access_token.
• “429 … rate limited”. Too many requests at once. Wait a minute, or add a Wait between runs.
• The run is blocked in the web app. Readwise runs through the browser extension. Install the extension and allow Readwise for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Readwise / Reader node

All connections

Create and manage credentials

Privacy & your data