# RSS and Apple review workflows for n8n and Make

Four importable templates for two Apify Actors. Each starts manually, uses your own Apify credential, and keeps its result inside your workflow tool. No email, external database or recurring schedule is configured.

[Download the complete ZIP](https://api.apify.com/v2/key-value-stores/IQa7iF8xgAsSffUKz/records/integration-workflows.zip?attachment=true)

| Workflow | n8n JSON | Make blueprint | Expected output with included inputs |
|---|---|---|---|
| RSS ingestion | [Download](https://api.apify.com/v2/key-value-stores/IQa7iF8xgAsSffUKz/records/rss-ingestion.n8n.json?attachment=true) | [Download](https://api.apify.com/v2/key-value-stores/IQa7iF8xgAsSffUKz/records/rss-ingestion.make.json?attachment=true) | Up to 10 article records from BBC and Hacker News; metadata removed |
| Apple review roadmap | [Download](https://api.apify.com/v2/key-value-stores/IQa7iF8xgAsSffUKz/records/apple-review-roadmap.n8n.json?attachment=true) | [Download](https://api.apify.com/v2/key-value-stores/IQa7iF8xgAsSffUKz/records/apple-review-roadmap.make.json?attachment=true) | One structured report from up to 40 public reviews of app 310633997 |

## Before running

Create your Apify API token in your own account. Store it only in the workflow tool's credential or connection manager. These downloads contain no working tokens. After import, select the credential/connection in every Apify request module. An imported file is not connected or scheduled automatically.

The default spending ceiling is **$1 per Apify run**. This is a maximum budget, not a $1 fixed charge:

- RSS uses **$0.008 per dataset row**. Two feeds with five entries each normally produce 12 rows including two metadata rows: **$0.096**. Filtering metadata after the run does not remove those billed rows. Failed feeds can produce billed error rows.
- Apple review analysis uses **$0.25 per completed report**. The native Apple source and supplied-record analysis use the same existing report price.
- Make/n8n hosting or operation charges depend on your own provider/plan and are separate. Check each Actor's live Pricing tab before large batches.

[RSS Actor](https://apify.com/technicaldost/rss-feed-scraper) · [Apple review Actor](https://apify.com/technicaldost/app-review-feature-roadmap)

## Import into n8n

1. Create a workflow and choose **Import from File**, then select the appropriate n8n JSON.
2. Create an **HTTP Header Auth** credential with header name `Authorization` and value `Bearer YOUR_APIFY_TOKEN`, replacing the placeholder in the credential manager only.
3. Select that credential in **Start Actor**, **Get run status**, and **Get dataset**. The exported credential reference is deliberately a placeholder.
4. Review the **Start Actor** JSON body. For Apple analysis, replace `appIds` and `country` to analyze your own app. For RSS, replace `feedUrls`.
5. Choose **Execute workflow**. The terminal node contains the article items or the intact Apple report plus readable Markdown. Connect your chosen destination only after inspecting this output.

n8n starts the Actor once, polls its status with a bounded loop, and reads the dataset only after success. It stops on failed/aborted/timed-out runs, API errors, missing output or truncated results. It never automatically retries the paid start request.

## Import into Make

1. Create a blank scenario, open its scenario menu, choose **Import Blueprint**, and upload the appropriate Make JSON.
2. Select or create your **Apify connection** in the Apify modules. Review the Actor and input JSON after connection selection; Make can refresh dynamically generated fields.
3. Keep scheduling **OFF** and choose **Run once** for the first test. The templates do not enable a recurring schedule.
4. Inspect the final output bundle before adding a destination such as a spreadsheet or database.

The native Make run waits synchronously with a bounded Actor timeout. A run/API/source failure must stop the scenario rather than publish partial or misleading output. If Make times out after starting the Actor, inspect the run in Apify before trying again. Stopping a workflow or using an error handler does not reverse an already started external Actor or its legitimate charges.

## Output and repeat use

RSS outputs `type=feed_item` records, including available title, URL, publication date, summary, full content and source feed. Missing publisher fields can be empty. Any feed error is surfaced instead of silently discarded. A repeat scrape can return the same articles; this Actor does not maintain a cross-run seen-item history. For downstream deduplication, use `feedUrl` plus `guid`, falling back to the article link.

Apple output preserves the report's nested `insights`, evidence and provenance. Scores are English-oriented deterministic research heuristics; this workflow does not call a generative AI model. The native feed is a bounded sample, not complete review history. Availability and finding counts can change.

These are bounded starter templates. If you increase feed counts, item counts or input volume, deliberately adjust the dataset-fetch limit/pagination and your spending ceiling. Do not add a `fields` or `view` projection before the RSS error check: that could hide its record-type field. Check error paths before connecting a destination that performs external writes.

## Recovery

- **401/403:** reselect a valid credential and confirm access to the Actor. Do not paste tokens into the workflow JSON or a URL.
- **Budget validation error:** RSS requires a maximum budget of at least $1 under its current configuration. That remains a ceiling, not a minimum bill.
- **Network timeout after start:** check Apify Runs first. Retrieve results from the existing run if it succeeded; do not blindly start another paid run.
- **Failed source:** inspect the source URL/app ID/storefront and the run log. RSS can return error rows even when its overall run status is successful.
- **Truncated/empty dataset:** inspect the run and fetch settings. Raise limits intentionally or add pagination; an empty result is not a successful Apple report.

## Validation and sources

The packaged validation report distinguishes live Apify API checks, fixture/guard tests, n8n import/runtime tests where completed, and Make validation. Make's authenticated scenario import/execution requires your account and is not claimed merely from a JSON check.

Official references: [n8n workflow import](https://docs.n8n.io/workflows/export-import/), [Apify n8n integration](https://docs.apify.com/integrations/n8n), [Make blueprint import](https://help.make.com/blueprints), [Apify Make integration](https://docs.apify.com/integrations/make).