Resources · Make integration

Pushinator Make integrationAutomate Pushinator with Make.

What if your alerts went out on their own when something changed? The Pushinator Make integration gives you 2 action modules, one to send a notification and one to call the Pushinator API. This page walks you through the connection, a first scenario and the traps to avoid.

Try the Pushinator integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pushinator Make integration do for you?

The Pushinator Make integration lets a Make scenario (the automation you build, a chain of steps) send a Pushinator notification without any code. Pushinator has no trigger of its own in Make, so another app or Make's schedule starts the flow, and Pushinator delivers the message at the end.

Hear about a failed payment before the customer writes in. Your billing tool spots the failure, and the Send a Notification module pushes a short alert with the amount and the customer name mapped from the previous step.

Get pinged when a hot lead fills your form. A form or CRM app starts the scenario, and Pushinator tells you who just signed up.

Reach a Pushinator feature the modules do not list. Make an API Call reuses your connection and calls any endpoint of the Pushinator API, so you are not stuck with a single module.

Keep one limit in mind: Make marks its own Pushinator documentation as limited, because little public information exists about the app. Expect to test with Run once rather than follow a detailed guide. If you are still weighing the tools, the n8n vs Make comparison and the Make review help you decide, and Make training covers the editor from scratch.

Connect

How do you connect Pushinator to Make?

  1. 01

    Add a Pushinator module

    In your scenario, click the + and search for Pushinator, then pick a module. Make asks for a connection (your Pushinator account linked to Make once, then reused by both modules). Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, such as the workspace it belongs to. Then either approve access on the Pushinator page that opens or paste the key Pushinator gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Once the connection exists, the module shows the fields it needs and Make can suggest values it reads from your account. Both modules will reuse it from now on.

First scenario

Your first scenario with Pushinator and Make

GoalWhen a new record lands in another app you already use, Make sends you a Pushinator notification about it.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. Click the + in the middle of the editor to place the first module, which here belongs to another app.

  2. 02

    Pick what starts the flow

    Choose the trigger of the app where the event happens, for example your form tool or your billing app, and connect that account. Pushinator cannot start the scenario itself.

  3. 03

    Add Send a Notification

    Click the + on the right of the first module, search for Pushinator and pick Send a Notification. Link your connection, then map data from the first module into the fields.

  4. 04

    Test with Run once

    Click Run once and trigger a real event in the source app. Open the bundles (the items passed between modules) to see exactly what each module received and sent.

  5. 05

    Schedule and switch it on

    If the first module is a scheduled trigger (clock badge), open its clock: it checks every 15 minutes by default, also the shortest interval on the Free plan. Then switch the scenario on.

Modules

What the Pushinator modules do

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

Pushinator1

Make an API Call

ActionIn the docs only

This module opens the whole Pushinator API from your scenario, using the same connection as the other module, so you can reach an endpoint that Make does not wrap in a ready module.

When to use it
pick it once Send a Notification cannot do what you need and you know which Pushinator endpoint to call.
Watch out
Make gives no detail on the Pushinator API, so the endpoint and its parameters come from Pushinator itself; test each call with Run once first.
Pushinator2

Send a Notification

ActionIn the docs only

Here is the module that puts a Pushinator alert in front of you, built from whatever the earlier modules found: a name, an amount, a status. It is the natural last step of most Pushinator scenarios.

When to use it
choose it whenever an event elsewhere deserves your attention, like a failed payment or a new signup.
Watch out
every notification counts as one operation (one run of one module), so start from an event that really matters, not from every single record.
Need help

Need help automating Pushinator with Make?

A person reads every message.

FAQ

Pushinator and Make: common questions

01Is the Pushinator Make integration free?
Yes, Pushinator is a standard app in Make, so you can use it on the Free plan. That plan comes with 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. Each module run counts as one operation against your plan. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow up to 40 minutes of execution.
02What do you need to connect Pushinator to Make?
You need a Pushinator account and a Make account. Make publishes no specific prerequisite for Pushinator, and its documentation for the app is marked as limited. The generic flow applies: add a Pushinator module, click Create a connection, give it a name if you want, authorize Make on the Pushinator page or paste the key Pushinator provides, then click Save. Both modules then reuse that single connection, so you only do this once per Pushinator account.
03Can Pushinator start a Make scenario by itself?
No. Pushinator has no trigger module in Make, only 2 actions. Your scenario starts from the trigger of another app, such as a form, a store or a CRM, or from Make's own schedule. A new scenario checks every 15 minutes by default, and the Free plan does not go below that. Paid plans can run it as often as every minute. If the source app has an instant trigger (lightning badge), the scenario starts as soon as the event happens.
04What if the Pushinator module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Pushinator API with the connection you already set up, so you are not limited to Send a Notification. Keep in mind that Make's documentation on Pushinator is limited, so the endpoint details have to come from Pushinator. Test the call with Run once and check the bundle it returns before you switch the scenario on, so a wrong parameter shows up during the test.
05Make or n8n for Pushinator?
It depends on where your other automations already live. In Make, Pushinator offers 2 modules, Send a Notification and Make an API Call, and runs on the Free plan as a standard app. The same app often has an n8n node too, but check n8n's node list before assuming so. Pick the tool your team already uses for the apps that trigger your alerts, since that is where most of the scenario will sit.
Same platform

Other docs you might need on this stack.

Browse all integrations