Resources · Make integration

PushEngage Make integrationAutomate PushEngage with Make.

Can Make send your PushEngage notifications for you? Yes: the PushEngage Make integration gives you 6 modules, 4 actions and 2 searches, to draft, schedule or send alerts and read their analytics. This guide connects your account and builds a first scenario with you.

Try the PushEngage integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PushEngage Make integration do for you?

The PushEngage Make integration links your PushEngage account to Make, so notifications get created and measured without you opening the PushEngage dashboard. You build a scenario (the automation Make runs, a chain of bricks called modules), and each module drafts, schedules, sends or measures a push for you.

Every new article gets its alert. When your blog or CMS publishes something, a scenario starts on that other app and Create a Draft Push prepares the notification in PushEngage, so someone can check it there before it goes out.

Launches announced at the right moment. Create a Scheduled Push sets up a notification now and lets PushEngage send it later, while Create a Sent Push goes straight to all subscribers when the news cannot wait.

Numbers back in your reporting. Get Summary Analytics returns a summary for the date range you pick, and Get Analytics of Push lists the notifications created by type, ready to land in a table through the Airtable Make integration.

What it does not do: PushEngage has no trigger in Make, so no PushEngage event can start a scenario; it starts on another app or on a schedule. When a listed module falls short, Make an API Call reaches the rest of the PushEngage API with the same connection. Many apps also have an n8n node; the n8n vs Make comparison lays out both tools, and the Make training helps if Make is new to you.

Connect

How do you connect PushEngage to Make?

  1. 01

    Copy your API key from PushEngage

    Everything starts with an active PushEngage account. In PushEngage, open Site Settings, then the Site Details page, and copy the API key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a PushEngage module in Make

    In your scenario, click the +, search for PushEngage and pick a module, for example Create a Draft Push. Then click Create a connection: the connection is your PushEngage account linked to Make once, and every PushEngage module reuses it.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name saves confusion once you have several. Paste the API key you copied and save. The module fields then open, ready to fill.

First scenario

Your first scenario: draft a push for each new article

GoalWhen a new article is published in another app, Make prepares the matching PushEngage notification as a draft.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario. The editor opens on an empty circle: click the + to place the first module, the one that starts everything.

  2. 02

    Start on the app that publishes

    PushEngage has no trigger, so the first module comes from another app: the one where your articles go live. Pick its trigger and connect that account the same way.

  3. 03

    Add Create a Draft Push

    Click the + on the right of the first module, search for PushEngage and choose Create a Draft Push. Select your connection, then map data from the article into the notification fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one article). Then look for the draft in PushEngage.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Set the interval you want, then switch the scenario on.

Modules

What each PushEngage module does

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

PushEngage1

Create a Draft Push

Action

In Make“Creates new notifications and can be saved as draft in PushEngage”

You get a notification ready in PushEngage that has not gone out yet: Create a Draft Push saves it as a draft, so a person can reread it, fix it and release it when it looks right.

When to use it
the text comes from an automatic source and your team wants a human check before it reaches subscribers.
Watch out
nothing is sent until someone sends the draft from PushEngage, so agree on who does it.
PushEngage2

Create a Scheduled Push

Action

In Make“Creates new notifications and can be scheduled for it to be sent”

A notification that leaves at the time you set, with nobody watching the clock: Create a Scheduled Push creates it now and hands PushEngage the job of sending it later.

When to use it
a sale, a webinar or a launch whose date is already known when the record is created.
Watch out
when the alert must go out right away, Create a Sent Push is the right module; this one exists to delay the send.
PushEngage3

Create a Sent Push

Action

In Make“Creates new notifications and can be sent to all subscribers”

Your subscribers see the alert straight away: Create a Sent Push creates the notification and sends it to all of them in the same step. It is the shortest path from an event to a message on their screens.

When to use it
breaking news, a restock or a price drop, where waiting for a review would cost the moment.
Watch out
it reaches every subscriber, so run your first tests with Create a Draft Push instead.
PushEngage4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the other five modules do not cover stays within reach: Make an API Call sends a request to any endpoint of the PushEngage API, reusing the connection you already have. No second key to paste.

When to use it
you need a PushEngage operation that has no dedicated module in the list.
Watch out
you write the request yourself, so keep the PushEngage API documentation open next to the module.
PushEngage5

Get Analytics of Push

Search

In Make“Gets list all notification created by each type”

The notifications PushEngage has created come back into your scenario, listed by type, ready for your reporting. Like every search module, Get Analytics of Push can return zero, one or several bundles.

When to use it
feeding a tracking sheet so you can compare notification types side by side.
Watch out
each bundle returned runs the next module once, and each run is an operation, the unit Make counts on your plan.
PushEngage6

Get Summary Analytics

Search

In Make“Gets analytics summary in the defined date range”

One overview for a period of your choice: Get Summary Analytics returns the PushEngage analytics summary between the dates you set. Handy when the question is how the channel did overall, not push by push.

When to use it
a wrap-up report after a campaign, with the date range matching the campaign itself.
Watch out
pick Get Analytics of Push instead when you need the list of notifications by type rather than a summary.
Need help

Need help automating PushEngage with Make?

A person reads every message.

FAQ

PushEngage and Make: common questions

01Is the PushEngage Make integration free?
Yes, on the Make side. PushEngage is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum interval of 15 minutes and at most 5 minutes per run. Paid plans (Core, Pro, Teams and Enterprise) go down to a 1 minute interval and remove the cap on active scenarios. Every module run is an operation counted on your plan. You still need an active PushEngage account with an API key, and its price is set by PushEngage, not by Make.
02What do you need to connect PushEngage to Make?
An active PushEngage account and its API key. In PushEngage, open Site Settings, then the Site Details page, and copy the key displayed there. In Make, add any PushEngage module, click Create a connection, give it a name if you like and paste the key. The connection is stored once, so every PushEngage module in every scenario reuses it without asking again. There is no webhook to create, since PushEngage has no instant module in Make.
03Can PushEngage start a Make scenario in real time?
No. PushEngage has no trigger module in Make, scheduled or instant, so no PushEngage event can start a scenario. There are two ways around it. Start on the trigger of another app, the one where your content or orders live, and put PushEngage in second position. Or start on a schedule: the clock on the first module runs the scenario every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. A Make webhook can also start the scenario when another tool calls it.
04What if a PushEngage module is missing in Make?
Use Make an API Call. It calls any endpoint of the PushEngage API with the connection you already have, so an action without a dedicated module stays within reach. The 6 listed modules cover drafting, scheduling and sending notifications, plus two analytics searches. The Make documentation lists no specific PushEngage limit, and it warns that its content is generated by AI from the PushEngage documentation, so confirm important details with PushEngage directly.
05Make or n8n for PushEngage?
It depends on your team and on the exact operations you need. Many apps also have an n8n node, so check both catalogs for the PushEngage actions you care about. On Make, you get 6 modules, no trigger, and Make an API Call for everything else, from the Free plan onward. Decide on concrete criteria: where your other automations already run, which editor your team knows, and whether the modules above cover your case. The comparison page on this site sets out both tools in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations