Inoreader
Utilities & PersonalTurn Inoreader feeds into an automation-ready content source. Agents pull the newest unread articles, subscribe to and unsubscribe from RSS feeds, browse folders and tags, star noteworthy items, and mark articles as read.
What This Integration Enables
Inoreader speaks the Google Reader dialect: feeds, folders, and tags addressed as streams, with read and starred states as markers. That vintage design turns out to be ideal for automation, because everything an agent needs, what is new, what is unseen, what matters, is queryable state. FlowRunner agents pull the newest unread items across an account, read any stream from a single feed to a curated folder, keep read state honest after processing, and manage the subscription list itself. - Surface the newest unread articles account-wide and route them downstream - Monitor specific feeds, folders, or tags and act on fresh content as it lands - Star noteworthy items and mark batches read to keep the inbox curated - Subscribe and unsubscribe programmatically as watch priorities shift - Build monitoring dashboards from per-feed and per-folder unread counts Nothing in this connector spends money or touches customers directly; the judgment concentrated here is editorial, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step sits where machine triage hands off to human curation.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The triage that keeps the reading list at zero
Every few hours, Get Unread Articles pulls what arrived, the agent classifies and summarizes each item, and the digest posts to [Slack](/integrations/slack) sorted by relevance. Mark As Read runs on the processed batch, so the account's unread state always means "not yet triaged" rather than "nobody got to it". The team consumes conclusions on their schedule instead of skimming feeds on the content's schedule.
From curated folder to publishable draft
The News folder, addressed as its label stream, feeds Get Stream Contents on a daily pull. Summaries land as a digest page in [Notion](/integrations/notion), and items an editor confirms get Star Article as the shortlist marker. When roundup day comes, the starred stream is the draft's raw material, and each included source logs to [Google Sheets](/integrations/google-sheets) for the citation record. The roundup assembles from a week of accumulated judgment instead of a Friday scramble.
Watchlist changes as a managed process
When the team picks up a new competitor or topic, the agent proposes feed candidates, and approved ones go live through Subscribe To Feed, filed into the right folder. Quarterly, Get Unread Counts and subscription activity identify feeds that produce nothing worth triaging; the pruning list gets human sign-off before Unsubscribe From Feed runs. The monitored surface expands and contracts with actual priorities, deliberately.
Human-in-Loop Highlight
Unsubscribe From Feed permanently removes a subscription from the account, and the loss is sneakier than it looks: the feed's place in the folder structure, its role in streams other automations read from, and the historical judgment of whoever added it all disappear with one call. An agent optimizing for a tidy list will happily prune the low-volume feed that exists precisely because it publishes twice a year and matters both times. So subscription removal is always a proposal with evidence: feed, folder, items produced in the window, and how many of those survived triage. A person who knows why the list looks the way it does approves the cut. The same editorial gate covers what gets starred into the publishing pipeline; the agent nominates, marks, and files at machine speed, and the human owns the line between monitored and published.
Agent Capabilities
10 actionsUser
1- Get User Info Retrieves the authenticated account's profile: user ID, name, email, sign-in status, and locale. The connection check and personalization source.
Subscriptions
3- List Subscriptions Lists all feed subscriptions with stream ID, title, feed URL, site URL, icon, and folder membership. The audit view of what the account follows.
- Subscribe To Feed Subscribes to an RSS or Atom feed by URL or prefixed stream ID, with an optional custom title and folder placement.
- Unsubscribe From Feed Permanently removes a subscription from the account. Runs inside reviewed pruning batches; the operation this page's gate covers.
Streams
3- Get Stream Contents Retrieves articles from any stream: a feed, a folder or tag label, or a system stream, with read-state filtering, sort order, item limits, and continuation-token pagination.
- Get Unread Articles Retrieves unread items across the whole account, newest first, as a convenience wrapper over the reading list. The default entry point for triage workflows.
- Get Unread Counts Retrieves unread counts per feed, folder, and tag with the newest-item timestamp for each. The dashboard read that shows where attention is owed.
Folders and Tags
1- List Folders and Tags Lists the account's folders and tags with their label stream IDs, each usable as a stream to read from.
Articles
2- Mark As Read Marks articles read or unread by item ID, singly or in batches. The state discipline that keeps triage idempotent.
- Star Article Stars or unstars articles by item ID. The bookmark signal that feeds curation pipelines and roundup drafts.
Frequently Asked Questions
What can FlowRunner do with Inoreader?
FlowRunner agents can run Get User Info, List Subscriptions, and Subscribe To Feed in Inoreader, plus 7 more actions.
Does connecting Inoreader to FlowRunner require OAuth?
Yes. Inoreader connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Inoreader trigger a FlowRunner workflow automatically?
Inoreader doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Inoreader
$100 in credits. No card required. Connect in minutes.