The original Pocket-to-Teams recipe no longer works. Mozilla shut Pocket down on 8 July 2025, and Make now says its Pocket integration is no longer useful.
Do not rebuild the old scenario. Replace it with a source your organisation controls.
The simplest replacement
Use a SharePoint list as the team reading queue. Create these columns:
| Column | Type | Purpose |
|---|---|---|
| Title | Single line of text | Article title |
| URL | Hyperlink | Original article |
| Summary | Multiple lines of text | Why it matters |
| Topic | Choice | Filtering and views |
| Submitted by | Person | Ownership |
| Shared to Teams | Yes/No | Prevent duplicate alerts |
People can add links through the list form. If capture speed matters, put the list in a Teams tab or create a small Power App later. Start with the list because it is easy to inspect and repair.
Notify Teams with Power Automate
- Create an automated cloud flow using SharePoint's When an item is created trigger.
- Select the site and reading-list name.
- Add Microsoft Teams > Post message in a chat or channel.
- Select the Team and channel.
- Build a short message from Title, Summary, URL and Submitted by.
- Update the list item and set Shared to Teams to Yes.
- Test with a real item, then inspect the flow run and the resulting link.
Microsoft's Teams connector documentation says posting actions require the Workflows app to be allowed in the Teams admin centre. It also documents message-size and cloud limitations. If the action is missing or fails, check tenant policy before rewriting the flow.
If you prefer Make
Make documents a SharePoint Watch Items module and a Teams Send a Message module. That creates the same pipeline, but it introduces a third-party processor and separate connection permissions.
Use one automation platform, not both. Power Automate is normally the simpler choice when the source and destination are already in Microsoft 365.
Keep the queue useful
Automation cannot decide whether a link deserves attention. Ask submitters for a one-sentence explanation and use a Topic choice instead of auto-generated tags. Add a weekly view of items that were submitted but never discussed.
That gives the team a searchable record rather than another stream of links that disappears up the chat.
Need help turning the list into a reliable, governed flow? Join Power Automate Builders.