The clean pattern is simple: save a useful article to a Feedly board, let Make detect that board item, check SharePoint for the same source ID or canonical URL, then create one review item.
This is curation, not automatic republication. Store the link and enough metadata to review it. Do not copy an article's full text into SharePoint unless you have the right to do so.
Fact-checked against current Make, Feedly integration and Microsoft SharePoint documentation on 24 August 2026. Make and Feedly plans change, so this guide makes no quota or price promise.
What you need
- a Feedly account with access to the board or feed you want to monitor;
- a Make account;
- a Microsoft 365 account allowed to connect to the destination SharePoint site;
- permission to create items in the target list;
- approval from whoever governs third-party connections to Microsoft 365.
The Make documentation lists Feedly triggers including New article in board and Watch articles. It also documents Microsoft SharePoint Online modules that can create, retrieve and update list items.
Design the SharePoint list first
Create columns such as:
| Column | Purpose |
|---|---|
| Title | Article title |
| Source URL | Clickable original link |
| Source ID | Feedly or integration identifier |
| Source name | Publisher or feed |
| Published date | Date supplied by the source |
| Saved date | When the curator saved it |
| Summary | Your short review note, not copied article text |
| Review status | New, Keep, Reject, Published |
| Processing key | Stable duplicate-prevention value |
Make Processing key unique if your SharePoint design permits it. A canonical URL is useful, but URLs can contain tracking parameters or change. Prefer the source's stable item ID when it is present.
Build the Make scenario
- In Make, create a new scenario.
- Add Feedly as the first app.
- Choose New article in board when a human saving an article is your quality gate.
- Connect the approved Feedly account and select the board.
- Run the module once with a test article so Make can expose its fields.
- Add a SharePoint search or retrieval step to look for the processing key.
- Add a filter that continues only when no matching item exists.
- Add the SharePoint module that creates a list item.
- Map only the fields you need.
- Run once, inspect the resulting item, then schedule the scenario.
Make's current Feedly documentation says its public detail is limited. Treat module names and returned field shapes as live configuration, not permanent API contracts. Capture a test bundle before mapping production fields.
Avoid duplicate articles
Duplicate prevention needs two layers:
- Scenario check: search for the processing key before creating the item.
- Data-store guard: make the key unique or otherwise reject duplicate writes.
The second layer matters when two scenario executions overlap. A search followed by create is not atomic by itself.
Normalise URLs before using them as a fallback key. Remove known campaign parameters only when doing so will not change the destination.
Map dates and links carefully
Store source dates separately from ingestion dates. Convert timestamps explicitly and keep UTC in the data layer where practical.
Use a SharePoint Hyperlink column for the source URL. Test the exact value the Make SharePoint module accepts in your tenant. Do not assume an undocumented JSON object is required.
Handle failures without losing the article
Add a Make error route that records:
- the source ID;
- failed module;
- safe error summary;
- retry status; and
- execution timestamp.
Do not log connection tokens, article contents or personal Feedly notes in a broadly accessible list.
Retry only errors that are genuinely transient. A 403 permission error or invalid field mapping needs correction, not repeated calls.
A Microsoft-only alternative
If the source exposes a normal RSS feed, Power Automate's Microsoft-published RSS connector can trigger when a feed item is published and write the item to SharePoint.
Microsoft documents an important limitation: the trigger relies on the feed item's pubDate, and items can be skipped when timestamps are not greater than previous ones. RSS is a useful simpler route, but it is not the same as a human-curated Feedly board.
Security and governance checks
- Use a dedicated integration identity where your policies allow it.
- Grant only the SharePoint access the scenario needs.
- Review the OAuth scopes before approving the connection.
- Decide who owns the scenario when its original maker leaves.
- Export or document the field mapping and duplicate rule.
- Test removal of Feedly or SharePoint access.
Sources
- Make Feedly app documentation
- Make Microsoft SharePoint Online documentation
- Microsoft SharePoint connector reference
- Microsoft RSS connector reference
Make the curation flow supportable
If you are deciding between Make and Power Automate, bring the trigger, permissions and duplicate rule to the Power Automate Builders Space. The Make signup links above retain Collab365's affiliate attribution; the Space link has separate article attribution.