Send articles to your read-later apps.

SlashFeed hands articles off to the read-later and bookmarking services you already use — Pocket, Instapaper, Wallabag, Readwise Reader, and Pinboard. Connect a service once, then send from the reader or automatically from a rule. Your credentials are encrypted at rest.

Open Read-Later Services

In the app, open Read-Later Services from the sidebar (under Automations). You'll see a card for each supported provider. Each card asks for the credentials that provider needs — fill in the one(s) you use and click Save. Secret fields are stored encrypted (AES-256-GCM) and never shown back to the browser.

Screenshot placeholder

SlashFeed's Read-Later Services page showing a card for each provider — Pocket, Instapaper, Wallabag, Readwise Reader, and Pinboard — with credential fields and Save / Test connection buttons.

priv/static/images/how-to/read-later-01-services-page.png

Get each service's credentials

Pocket

Create an application at getpocket.com/developer to get a consumer key, then run Pocket's OAuth flow once to obtain an access token. Paste both into the Pocket card:

consumer_key
access_token

Instapaper

Instapaper's simple save API uses your account login directly — just your username / email and password. No developer registration needed.

username
password

Wallabag

In your Wallabag instance, open Developer → create a new API client, then use it to obtain an OAuth access token. Enter your instance URL and the token:

base_url       (e.g. https://app.wallabag.it)
access_token

Readwise Reader

Copy your access token from readwise.io/access_token and paste it into the Readwise card:

token

Pinboard

Grab your API token from pinboard.in/settings/password. It looks like username:XXXXXXXXXXXX — paste it verbatim:

auth_token     (e.g. maria:A1B2C3D4E5F6)
Screenshot placeholder

A close-up of one provider card (e.g. Readwise Reader) with its access-token field filled in and the Save button, illustrating where the credentials go.

priv/static/images/how-to/read-later-02-fill-credentials.png

Test the connection

After saving, click Test connection on the card. SlashFeed sends a canary URL to the service and reports back whether it succeeded — so you know the credentials are right before you rely on them.

Screenshot placeholder

The provider card after clicking Test connection, showing a green success flash and a 'Connected' badge next to the provider name.

priv/static/images/how-to/read-later-03-test-connection.png

Send articles — by hand or automatically

Send an article to a connected service straight from the reader, or make it automatic: open the automation canvas, add a Send to Read-Later action, pick the provider, and choose what triggers it — every new entry, one feed, or a whole category. Deliveries run in the background with retries.

Screenshot placeholder

The automation canvas with a 'Send to Read-Later' action node selected, its config drawer open showing the provider dropdown (Pocket / Instapaper / Wallabag / Readwise / Pinboard), wired to a new-entry trigger.

priv/static/images/how-to/read-later-04-automation-action.png
Private by design. Credentials are encrypted at rest and never leave your instance except to call the service you chose. Disconnect any service at any time from the same page. The same automation action works alongside Telegram, Slack, and webhook actions.