Resources · Make integration

Pocket Alert Make integrationAutomate Pocket Alert with Make.

Get a Pocket Alert message when something happens in another tool. The Pocket Alert Make integration gives you 3 action modules, two for messages and one for the raw API. This guide links your account, then walks you through a first working scenario.

Try the Pocket Alert integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pocket Alert Make integration do for you?

The Pocket Alert Make integration lets a Make scenario send messages through your Pocket Alert account, with or without an image. A scenario is the automation you build in Make: a chain of modules, where each module is one brick, such as a trigger from another app or a Pocket Alert action. Pocket Alert has no trigger of its own, so it always sits at the end of the chain.

A heads-up when a lead fills your form. Put the form tool's module first, then Send a Message with the lead's name mapped into the text. Each lead becomes one bundle, the item that flows from one module to the next, and one alert.

A visual alert for a store. When an order or a product photo arrives from another app, Send a Message with an Image carries the picture along with the text, so the person reading it sees what it is about without opening anything.

Anything the listed modules skip. Make an API Call reaches any endpoint of the Pocket Alert API with the same connection, which covers the cases the two message modules leave out.

What Make does not do here: it cannot start a scenario from Pocket Alert, because the app offers no trigger in Make. The public documentation of the app is also thin, so check the fields in the module itself. Before choosing a plan, read the Make pricing page; if you hesitate between tools, the n8n vs Make comparison lays out the criteria, and Make troubleshooting helps when a run fails.

Connect

How do you connect Pocket Alert to Make?

  1. 01

    Copy your API key from Pocket Alert

    You need an active Pocket Alert account. Open its account settings page, go to the API Keys section and copy the key shown on screen. Keep it at hand, Make asks for it in the next step.

  2. 02

    Open the connection window in Make

    Add any Pocket Alert module to your scenario and click Create a connection. A connection is your Pocket Alert account linked to Make once, then reused by every Pocket Alert module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the API key you copied, or follow the instructions shown on screen, and save. The module is now ready to fill.

First scenario

Your first scenario with Pocket Alert

GoalWhen something happens in another app, Make sends a Pocket Alert message about it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where the event starts, such as your form or your store.

  2. 02

    Add Send a Message

    Click the + on the right of that first module, search for Pocket Alert and choose Send a Message. Select your connection, or create it as shown above.

  3. 03

    Map the message text

    Fill the module fields and drop values from the first module into the text, for instance a customer name or an order reference. Each alert then tells the reader what actually happened.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Make shows the bundles each module received; check that the message reached Pocket Alert with the right content.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation, which is what Make bills on your plan.

Modules

What Pocket Alert can do in Make

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

Pocket Alert1

Make an API Call

ActionIn the docs only

This module opens the whole Pocket Alert API to your scenario and reuses the connection you already created, so there is no second login to manage.

When to use it
pick it only when neither message module offers the request you need, since it asks you to know the endpoint you are calling.
Watch out
the Make documentation for this app lists no endpoint, so check with Pocket Alert which request to send before building the call.
Pocket Alert2

Send a Message

ActionIn the docs only

With Send a Message, a line of text built from your scenario lands in Pocket Alert, carrying whatever you mapped from earlier modules: a name, an amount, a status.

When to use it
this is the default choice for plain alerts, such as a new form entry, a failed payment or a ticket marked urgent in another tool.
Watch out
one bundle means one message, so a module upstream that returns many items sends many alerts.
Pocket Alert3

Send a Message with an Image

ActionIn the docs only

You get an alert that shows a picture next to the text, which helps the reader recognize a product, a receipt or a screenshot at a glance.

When to use it
choose it over Send a Message when the earlier module already provides an image, for example a photo uploaded through a form.
Watch out
click Run once and check in the bundles that an image really came through, because an empty mapping leaves nothing to display.
Need help

Need help automating Pocket Alert with Make?

A person reads every message.

FAQ

Pocket Alert and Make: frequent questions

01Is the Pocket Alert Make integration free?
Yes, on the Make side. Pocket Alert is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 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 lower the interval to 1 minute and remove the cap on active scenarios. Your Pocket Alert subscription is a separate matter, described on the pricing page of Pocket Alert itself.
02What is needed to connect Pocket Alert to Make?
You need an active Pocket Alert account and its API key. In Pocket Alert, open the account settings page, go to the API Keys section and copy the key. In Make, add a Pocket Alert module, click Create a connection, give it a name if you like, and paste the key. The same connection then serves the three Pocket Alert modules, so you only do this once per account, even when several scenarios send alerts.
03Does Pocket Alert trigger a Make scenario in real time?
No. Pocket Alert has no trigger module in Make, so it cannot start a scenario on its own. The scenario starts from another app instead: an instant trigger, which that app calls through a webhook as soon as something happens, or a scheduled trigger that Make checks every 15 minutes by default. Pocket Alert then comes in as the action that sends the message at the end of the chain.
04What if a Pocket Alert module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Pocket Alert API with the connection you already have, so you can cover requests that Send a Message and Send a Message with an Image do not handle. You need to know which endpoint to call, so check with Pocket Alert which request fits your case. Make also warns that its documentation for this app was generated automatically and may contain mistakes, so check important details with Pocket Alert.
05Make or n8n for Pocket Alert: which one fits?
It depends on how you like to build. In Make, the integration offers three ready modules and a visual editor where you add each brick, test with Run once and switch the scenario on. n8n often has a node for the same app, which is worth checking for Pocket Alert before you decide. Compare the two on the modules available for your case, the plan limits you would hit and the way each editor fits your team.
Same platform

Other docs you might need on this stack.

Browse all integrations