Resources · Make integration

Pocket Make integrationAutomate Pocket with Make.

What if your reading list sorted itself? The Pocket Make integration gives you 9 modules: 1 trigger, 7 actions and 1 search. This guide is for people who already save articles in Pocket, and it walks you from the connection to a first working scenario.

Try the Pocket integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pocket Make integration do for you?

The Pocket Make integration links your Pocket account to Make so that saved items can start or feed a scenario, the automation you build in Make as a chain of modules. Each module is one brick: a trigger that watches Pocket, an action that changes an item, or a search that finds items. No code is involved.

A reading list that tags itself. Watch items spots each new save, then Modify item tags labels it so a research team finds every source under the right topic without sorting by hand.

Links from other tools, collected in one place. A content marketer can send links coming from another app into Pocket with Add an item, so every reference lands in the same list. The Airtable Make integration is one possible source.

A tidy archive. Get items finds the items that match a filter, and Archive an item or Mark as a favorite then moves or flags each one, so the list you open stays short.

Know the limits before you build. Pocket's trigger is scheduled, not instant, and this app has no Make an API Call module, so you work with the 9 modules listed below. The Make documentation page for Pocket also says it was generated with AI from Pocket's own docs, so check important details against Pocket. The same app often exists in n8n too; the n8n vs Make comparison lays out the criteria. For a guided start, see the Make training.

Connect

How do you connect Pocket to Make?

  1. 01

    Register a Pocket developer application

    Make needs an active Pocket account and a developer application. In the developer section of Pocket, click Create an Application or open an existing one, enter the callback URI https://www.integromat.com/oauth/cb/pocket, then copy the Client ID.

  2. 02

    Add a Pocket module and open the connection

    In your scenario, add any Pocket module and click Create a connection. A connection is your Pocket account linked to Make once, then reused by every Pocket module. You can type a label in Connection name.

  3. 03

    Paste the credentials and authorize

    Enter the credentials you copied from your Pocket developer application, or follow the instructions Make shows on screen. Once the connection is created, it appears in the module and you can pick it in every other Pocket module.

First scenario

Your first scenario with Pocket

GoalWhen you save a new item in Pocket, Make adds the tags you chose so it lands in the right topic.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first slot is where the trigger goes.

  2. 02

    Add Watch items

    Search for Pocket, pick Watch items and select the connection you created. From now on, each new item Make finds in Pocket travels through the scenario as a bundle, one item at a time.

  3. 03

    Add Modify item tags

    Click the + to the right of the trigger, choose Modify item tags, then map the item coming from Watch items and type the tag you want Pocket to apply to it.

  4. 04

    Test with Run once

    Save an article in Pocket, then click Run once. Make runs the scenario one time and shows the bundle each module received, so you can check that the tag landed on the right item.

  5. 05

    Schedule and switch on

    Click the clock on Watch items to set the schedule. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Then switch the scenario on.

Triggers

What starts a Pocket scenario

1 module starts a scenario when something happens in Pocket. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pocket as soon as it happens.

Pocket1Watch items

Watch items

Scheduled trigger

In Make“Trigger when a new item is created.”

Watch items gives your scenario a starting point every time a new item shows up in your Pocket account. Each new save becomes a bundle, which the following modules can tag, archive or copy to another tool.

How it fires
scheduled. Make checks Pocket on the scenario's schedule, every 15 minutes by default, so a new item waits for the next check instead of arriving instantly.
When to use it
you want something to happen after each save, such as tagging an article or logging it in a shared table.
Watch out
each module run on each item counts as one operation on your Make plan, so a busy reading list uses more of your monthly credits.
Modules

What Make can do in Pocket

Pocket gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Pocket1

Add an item

Action

In Make“Adds a new item.”

Add an item saves a new item in Pocket from data sent by any earlier module, so links found elsewhere end up in your reading list without copy and paste.

When to use it
a form, a newsletter parser or a spreadsheet produces links that someone on the team should read later.
Watch out
the module only adds; if the same link can arrive twice from your source, filter duplicates earlier in the scenario.
Pocket2

Archive an item

Action

In Make“Moves an item to the user's archive.”

Archive an item moves an item out of your list and into the Pocket archive, where it stays available but no longer clutters what you have left to read.

When to use it
an article has been processed, summarized or shared, and you want the list to show only what still needs attention.
Watch out
archiving is reversible with Readd an item, which makes it the safer choice over deletion.
Pocket3

Delete an item

Action

In Make“Permanently removes an item from the user's account.”

With Delete an item, an item disappears from the Pocket account for good. That keeps the list and the archive free of links that no longer matter to anyone.

When to use it
links from a test run or from a source you stopped following should not stay anywhere in the account.
Watch out
the removal is permanent and cannot be undone from Make, so run the scenario once with Run once and read the bundles before you switch it on.
Pocket4

Mark as a favorite

Action

In Make“Marks an item as a favorite.”

Some saves matter more than others. Mark as a favorite flags an item in Pocket so those pieces stand out from everything else in your list.

When to use it
a condition in the scenario identifies a key source, for example an article that also went into your team's reference table.
Watch out
it only sets the flag. Add Modify item tags if you also want to remember why the item was picked.
Pocket5

Modify item tags

Action

In Make“Modifies item tags.”

Modify item tags changes the tags on an item, which turns a flat reading list into topics you can browse in Pocket without opening every article.

When to use it
right after Watch items, to label each new save by project, client or theme based on where the link came from.
Watch out
the module needs to know which item to change, so map the item from the trigger or from Get items instead of typing it by hand.
Pocket6

Readd an item

Action

In Make“Re-adds (unarchives) an item to the user's list.”

Readd an item brings an archived item back into your list, the reverse of Archive an item, so an old reference is in front of you again when it becomes useful.

When to use it
a topic comes back on the agenda, and Get items can find the archived articles that match it.
Watch out
it only works on items that were archived; a deleted item cannot be brought back this way.
Pocket7

Remove from the favorites

Action

In Make“Removes an item from the user's favorites.”

Remove from the favorites clears the favorite flag on an item, which keeps your favorites view limited to what still deserves it.

When to use it
a favorite has been read and shared, and you want the flag to reflect current priorities instead of old ones.
Watch out
the item stays in your list with its tags; to move it away as well, add Archive an item after this module.
Pocket8

Get items

Search

In Make“Returns items that match the given filter.”

Get items searches your Pocket account and returns the items that match the filter you set, which lets a scenario work on existing saves and not only on new ones.

When to use it
you want to archive, tag or favorite a whole set of items at once, such as every link under one tag.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, so the operation count grows with the results.
Need help

Need help automating Pocket with Make?

A person reads every message.

FAQ

Pocket and Make: frequent questions

01Is the Pocket Make integration free?
Yes, Pocket is a standard app, so it works on the Make Free plan. That plan has its limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. The Pocket subscription itself is a separate matter handled by Pocket.
02What do you need to connect Pocket to Make?
You need an active Pocket account and a developer application registered with Pocket. In the Pocket developer section, create an application or open one you already have, enter the callback URI given in the Make documentation, and copy the Client ID. Then add a Pocket module in Make, click Create a connection, give it a name if you like and enter the credentials or follow the on-screen steps. The connection is reused by every Pocket module afterwards.
03Does the Pocket trigger in Make fire instantly?
No. Watch items is a scheduled trigger: Make checks Pocket on the schedule of the scenario, and a new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed. Paid plans can go down to 1 minute. A new save therefore reaches your scenario at the next check. If you only need to act on existing items, you can skip the trigger and start with Get items on a schedule.
04What if the Pocket module you need is missing in Make?
It depends on what is missing. Pocket in Make has 9 modules and no Make an API Call module, so you cannot send a custom request to Pocket from the app itself. Start by checking whether two existing modules together cover the need, such as Get items followed by Modify item tags. If they do not, the step may belong in another app of your scenario. For a case that still does not fit, the Hack'celeration team can look at it with you.
05Should you use Make or n8n for Pocket?
It depends on your criteria rather than on a ranking. On the Make side, Pocket offers 9 modules with a scheduled trigger, 7 actions and a search, and it runs on every plan including Free. The same app often has an n8n node as well, so check what each tool offers for your exact use case. The practical questions are which platform your other automations already run on, and which modules your scenario needs. Neither tool is presented here as better.
Same platform

Other docs you might need on this stack.

Browse all integrations