# Inoreader integrations: subscriptions

> Add a feed in Inoreader. Connect Inoreader to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/inoreader-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Inoreader is a news and content reader that collects articles from feeds, newsletters, and websites into folders and tags for following topics. Tray.ai connects to Inoreader through the HTTP Connector, so your workflows can call the Inoreader API alongside the rest of your stack. API access comes through Inoreader's partner program or API plan, so you need approved credentials first.

## Use cases

### Subscriptions

Read, create, and update subscriptions in Inoreader from any Tray.ai workflow. The Inoreader API covers calls such as list feeds and add a feed.

- List feeds
- Add a feed
- Edit a feed

### Folders and tags

Read, update, and delete folders and tags in Inoreader from any Tray.ai workflow. The Inoreader API covers calls such as list folders and tags and rename a tag.

- List folders and tags
- Rename a tag
- Delete a tag

### Stream contents

Read and update stream contents in Inoreader from any Tray.ai workflow. The Inoreader API covers calls such as get stream contents and get item IDs.

- Get stream contents
- Get item IDs
- Get unread counts

### Preferences

Read and update preferences in Inoreader from any Tray.ai workflow. The Inoreader API covers calls such as list stream preferences and set stream preferences.

- List stream preferences
- Set stream preferences

## Challenges Tray.ai solves

### Keeping Inoreader credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Inoreader credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Inoreader API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Inoreader API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Inoreader?

Yes. Tray.ai connects to Inoreader through the HTTP Connector, which calls the Inoreader API directly. Any call the Inoreader API documents can run as a step in a Tray.ai workflow. API access comes through Inoreader's partner program or API plan, so you need approved credentials first.

### How does Tray.ai authenticate with Inoreader?

The Inoreader API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Inoreader connector?

Inoreader runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Inoreader connector from the Inoreader API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
