Overview
This node integrates with Miniflux, a feed reader service, allowing users to interact with their feeds, categories, and entries programmatically within n8n workflows. Specifically, the "Entry - Get Many" operation fetches multiple feed entries based on various filtering and sorting options.
Common scenarios where this node is beneficial include:
- Aggregating unread or read articles from specific feeds or categories for further processing.
- Extracting plain text content from feed entries for text analysis or summarization.
- Fetching original article HTML content for archival or display purposes.
- Automating feed monitoring and notifications based on entry status or publication date.
For example, you could use this node to retrieve the latest 50 unread entries from a particular category, extract their plain text, and then send summaries via email.
Properties
| Name | Meaning |
|---|---|
| Category | ID of the category to get entries for. Choose from the list or specify an ID using an expression. |
| Feed | ID of the feed to get entries from. Choose from the list or specify an ID using an expression. |
| Limit | Maximum number of results to return (minimum 1). Default is 50. |
| Order | Field to order the results by. Options: Category ID, Category Title, ID, Published At, Status. Default is ID. |
| Order Direction | Direction to order the results. Options: Ascending, Descending. Default is Ascending. |
| Original Article | Whether to fetch the original article HTML content through Miniflux. If enabled, the node will make additional requests to retrieve full article content. Default is false. |
| Plain Text | Whether to extract plain text from the entry content. If enabled, the node extracts and adds a plain text version of the content. Default is true. |
| Status | Filter entries by status. Options: Read, Unread, Removed. Default is Unread. |
Output
The node outputs an array of JSON objects representing feed entries. Each entry object includes fields returned by the Miniflux API such as:
id: Entry identifier.title: Title of the entry.content: Original HTML content of the entry.content_plain: Extracted plain text content (if enabled).published_at: Publication date/time.status: Read/unread/removed status.category_id,category_title: Category details.original_article_html: Full original article HTML content (if requested).original_article_plain: Plain text extracted from the original article (if both original article and plain text options are enabled).
If the "Original Article" option is enabled, the node performs additional API calls per entry to fetch the full article content.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Miniflux instance with valid API authentication credentials configured in n8n.
- Uses Miniflux REST API endpoints to fetch feeds, categories, and entries.
- The node depends on helper functions for making authenticated API requests and extracting plain text from HTML content.
Troubleshooting
- Empty results: Ensure that the selected category or feed IDs exist and contain entries matching the specified status filter.
- API request failures: Verify that the API key credential is correctly set up and has sufficient permissions.
- Performance issues when fetching original articles: Enabling the "Original Article" option triggers additional API calls per entry, which may slow down execution if many entries are fetched.
- Incorrect plain text extraction: The plain text extraction relies on HTML parsing; complex or malformed HTML content might not convert perfectly.
Common error messages may relate to authentication failures, invalid resource IDs, or rate limiting by the Miniflux API. Resolving these typically involves checking credentials, verifying input parameters, and respecting API usage limits.
Links and References
- Miniflux Official Website
- Miniflux API Documentation
- n8n Expressions Documentation (for dynamic parameter values)