Inoreader icon

Inoreader

Interact with the Inoreader API

Actions8

Overview

This node integrates with the Inoreader API to manage articles and their organization within a user's Inoreader account. Specifically, for the Article resource and the Add to Read Later operation, it allows users to add an existing article to their "Read Later" section by tagging it appropriately.

Common scenarios where this node is beneficial include:

  • Automatically marking important or interesting articles for later reading based on triggers or workflows.
  • Organizing articles by adding them to the "Read Later" list without manual intervention.
  • Integrating Inoreader with other tools to streamline content curation and consumption.

For example, you could use this node in a workflow that monitors RSS feeds and automatically adds certain articles to your Read Later list based on keywords or other criteria.

Properties

Name Meaning
Read Later Tag ID The internal tag ID representing the "Read Later" section in Inoreader. Defaults to user/-/state/com.google/starred. This is a hidden property set automatically.
Article ID The unique identifier of the article to be added to the Read Later section. Usually formatted like "tag:google.com,2005:reader/item/0000000a9de1460f". This ID can be obtained from previous operations such as fetching articles or triggers.

Output

The node outputs JSON data representing the response from the Inoreader API after attempting to add the article to the Read Later tag. The structure typically includes confirmation of the tagging action or error details if the operation failed.

No binary data output is produced by this operation.

Example output JSON snippet:

{
  "status": "OK"
}

or in case of error:

{
  "error": "Article ID is required for adding a tag!"
}

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests to the Inoreader API.
  • The node uses HTTP requests to interact with the Inoreader API endpoints.
  • No additional external dependencies are needed beyond the configured OAuth2 API credentials.

Troubleshooting

  • Missing Article ID: If the Article ID is not provided, the node will throw an error stating that the Article ID is required. Ensure you supply a valid article ID from prior steps or triggers.
  • Missing Tag ID: Although the Read Later Tag ID is usually preset, if missing, the node will error out. This is generally handled internally.
  • Invalid Article ID Format: The Article ID must follow the expected format (e.g., starting with tag:google.com,2005:reader/item/). Invalid IDs will cause the API call to fail.
  • Authentication Errors: If the API key or OAuth token is invalid or expired, the node will fail to authenticate. Reconfigure or refresh credentials as needed.
  • API Rate Limits or Network Issues: Temporary failures may occur due to network problems or API rate limits. Retrying the workflow might resolve these issues.

Links and References

Discussion