Collect vendor RSS updates with Make
Keep vendor updates in one private Sheet for review. This Make blueprint collects up to five feed items and skips links already recorded for that feed.
What you need
- Your own Make account, Google connection and private Google spreadsheet. Runs use your platform allowance.
- One public RSS or Atom feed you have checked and approved. The feed and article links must use the same lowercase HTTPS hostname.
Import this JSON file into a new inactive Make scenario. No account connection or private destination is included.
Download the Make blueprintImport the ten columns into a private tab named Updates. Keep the headers in order.
Download the Sheet headerThe text guide includes column mappings, controlled tests, date handling and stopping instructions.
Download the full setup notesLimits to keep in mind
- The scenario collects feed items for human review. A new feed item doesn't establish a product change.
- Make's RSS module has no enforced redirect or private-address restriction verified here. Use only an approved public feed. Leave the scenario off if your environment requires those controls.
- The scenario doesn't fetch linked articles or track edits at an existing URL. Five current items per run isn't a complete archive.
- Use one writer for the destination. Inspect the actual Sheet after an uncertain save before restarting.
- Atom publication dates stay blank. RSS publication dates require a raw publication field. Neither an intake date nor a feed date means a person reviewed the claim.
Keep source collection separate from a finding
Vendor announcements can identify something worth checking. They don't replace a dated product test. Use the saved links to decide what needs review, then record your findings in the Sheet.
This is a separate source-collection exercise from our Make vs n8n comparison. The download doesn't change the comparison's original recordings or findings.
Connect your own feed and private Sheet
The blueprint uses ordinary Tools, RSS, Google Sheets and an array aggregator. No AI service or custom receiver is needed.
- Create a private Google spreadsheet. Import the header file into a tab named Updates.
- Create a new inactive Make scenario. Import the blueprint and select your own Google connection in both Sheet modules.
- Open Set your feed and private sheet. Enter the approved feed URL, exact lowercase hostname, vendor label, spreadsheet ID and Updates. Leave configured=no.
- Confirm both Sheet modules use the same spreadsheet and tab. Keep the ten column mappings. The append module uses Unformatted: Yes, RAW and Insert rows.
- Keep Process data in order on and automatic retries off. Read the full setup notes before changing either setting.
Check the first save and the repeat
The imported file stays unconfigured. Your own connections and source still need a check before a schedule starts.
- With configured=no, run once. The first guard should pass no bundles and make no RSS or Sheet operations.
- Set configured=yes after checking the source and destination. Run once. Inspect the Sheet and confirm each row has the correct feed, article link, title and review-needed status.
- Run the same feed again. Already recorded feed/article pairs should add no rows. Check the Sheet before restarting if a save is uncertain.
- Choose a schedule that suits the feed activity and your allowance. To stop collection, turn the scenario off in Make.
The corrections passed the native checks
On 16 October 2026, we corrected the hostname guard, empty lookup handling and Google Sheets fields. Eleven corrected native runs passed 1,270 independent checks. A separate final guard and both journals passed 472 checks.
Make accepted a clean five-module import. Only the two expected recipient connection requirements remained. The execution checks used the configured owner scenario; the unconnected import was cancelled without running.
Real provider outages, simultaneous writers and uncertain writes remain untested. The full test record and setup notes preserve those limits.