Build a Useful Article Library in SharePoint Without Pocket

The original workflow used Pocket, which closed on 8 July 2025. A SharePoint article library still makes sense, but it needs a different capture source and better controls than the old recipe provided.

Start with the list, not the automation

Create columns for Title, Canonical URL, Why it matters, Topic, Source, Submitted by, Published date, Review status and URL key.

The URL key is a normalised version of the address used to find duplicates. Remove tracking parameters such as utm_source before saving it. Do not rely on the article title because publishers change titles and different pages can share one.

Choose a capture route

Manual capture

Use the list form or a small Power App. This is the most reliable starting point because the submitter can explain why the article deserves attention.

RSS capture

Use a publisher's official RSS feed where available. A scheduled cloud flow can read the feed, check the URL key and create only unseen items.

Make capture

Make documents Microsoft SharePoint Online modules including Watch Items, Create an Item and Update an Item. Use Make when the source has a supported module and your organisation permits the data connection.

Build the flow safely

1. Receive a URL from the chosen source.
2. Strip known tracking parameters and normalise the host casing.
3. Query SharePoint for the URL key.
4. Stop if a matching item already exists.
5. Create the item with Review status set to New.
6. Notify a reviewer, not the whole company.
7. Post to Teams only after the item is marked Keep.

Keep AI summarisation out of version one. It adds cost, data handling and a new failure mode before you know whether people use the library. A one-sentence human note is often more valuable because it explains the local relevance.

Permissions and failure boundaries

Use a connection owned by an accountable person or governed automation identity. Give it access only to the target site and list where possible.

Log the original URL and source event. If metadata extraction fails, save the item as New with an error note instead of discarding it. If the source later deletes or changes the article, your list should still show who submitted the link and why.

Create views for New items, each Topic and items not reviewed after a set period. Archive low-value entries instead of leaving thousands of dead links in the default view.

The automation gets content into SharePoint. Editorial ownership is what keeps the list valuable.

Need help with URL normalisation, duplicate checks or review notifications? Join Power Automate Builders.