Resources · Make integration

PostPulse Make integrationAutomate PostPulse with Make.

Can Make publish to PostPulse for you while you work elsewhere? The PostPulse Make integration gives you 6 action modules and no trigger. This page is for people who already use PostPulse and want to link the account, then build a first scenario that posts on its own.

Try the PostPulse integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PostPulse Make integration do?

The PostPulse Make integration links your PostPulse account to Make so that a scenario, the automation you build in Make, can act in PostPulse for you. It offers 6 action modules, each one a brick of the scenario, and none of them is a trigger, so something else has to start the run.

A post that leaves on its own. Another app starts the scenario, then Create a post sends the content to PostPulse. You write the text once, in the tool where it already lives.

Media that arrives before the post. Chain Upload a file and then Create a post, so the file is in PostPulse when the post needs it. Create a file import is the other route for bringing a file in.

A quick check of the account. Get connected accounts and Get chats read what PostPulse holds, which helps you choose where a post goes before you send it.

Two limits to keep in mind. PostPulse has no trigger in Make, so the scenario starts from another app or from a schedule. And the Make doc for this app is AI-generated from the PostPulse documentation, so check any detail that matters with PostPulse itself. When a module is missing, Make an API call reaches the rest of the PostPulse API with the same connection. If you are weighing tools, the n8n vs Make comparison and our Make review set the context, and Make pricing explains what a plan counts.

Connect

How do you connect PostPulse to Make?

  1. 01

    Add a PostPulse module

    You need an active PostPulse account and an API key from it first. In your scenario, add any PostPulse module and click Create a connection. A connection is your PostPulse account linked to Make once, then reused by every PostPulse module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name pays off the day you run several PostPulse accounts or share scenarios with a teammate. Something like the brand or the client works well.

  3. 03

    Paste your credentials

    Enter the credentials you copied from your PostPulse account, or follow the instructions Make shows on screen. Once saved, Make can read what the account holds and fill the lists in each module.

First scenario

Build your first scenario with PostPulse

GoalWhen a new item appears in another app, Make uploads its file to PostPulse and creates a post with it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that should start things, the tool where your content already lives, and its module.

  2. 02

    Add Upload a file

    Click the + to the right of the first module, search PostPulse and choose Upload a file. Create the connection if Make asks, then map the file from the previous module.

  3. 03

    Add Create a post

    Add Create a post after the upload. Fill its fields with data mapped from the earlier modules; Make lists what it can read from PostPulse once the connection exists.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items each module received and sent. Open them to confirm the file and the post look right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.

Modules

What each PostPulse module does

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

PostPulse1

Create a file import

ActionIn the docs only

You get a file import started in PostPulse from inside your scenario, without opening PostPulse. The Make doc gives no detail on it, so its fields are what Make shows once connected.

When to use it
when the file should come into PostPulse as an import rather than through Upload a file, compare both on a test file.
Watch out
run it with Run once and read the returned bundle before you rely on it.
PostPulse2

Create a post

ActionIn the docs only

Your content turns into a PostPulse post as soon as the scenario reaches this module, with the text and details mapped from earlier steps. It is the module most scenarios end on.

When to use it
when an article, a product or a message somewhere else should become a post without copy and paste.
Watch out
if the post needs media, place Upload a file before it so the file exists first.
PostPulse3

Get chats

ActionIn the docs only

This one hands your scenario the chats PostPulse holds for the connection, so later modules can use them. Its name says it reads rather than writes, which makes it a good first test (a deduction: the doc does not say).

When to use it
when you want to see what PostPulse returns for chats before building anything that depends on them.
Watch out
the doc does not describe the output, so check the bundles after Run once to see what comes back.
PostPulse4

Get connected accounts

ActionIn the docs only

With it, you see which accounts are linked to your PostPulse workspace, right inside the scenario. That answer helps you point a post at the right place instead of guessing.

When to use it
before Create a post, when one PostPulse login manages several accounts and you need to pick one.
Watch out
the doc does not describe what it returns, so read the bundles after Run once before mapping them.
PostPulse5

Make an API call

ActionIn the docs only

You reach any part of the PostPulse API that the five other modules leave out, with the same connection and no extra login. It is the fallback when the module you need is not in the list.

When to use it
when the PostPulse documentation shows an endpoint that no ready module covers.
Watch out
you write the request yourself, so keep the PostPulse API reference open and test with Run once.
PostPulse6

Upload a file

ActionIn the docs only

A file from another step of your scenario lands in PostPulse, ready for a post to use. Think of the attachment from an email or the image a form just received.

When to use it
right before Create a post, when the post should carry a picture or a document.
Watch out
on the Free plan Make handles files up to 5 MB, so a heavier file will not go through.
Need help

Need help automating PostPulse with Make?

A person reads every message.

FAQ

PostPulse and Make: common questions

01Is the PostPulse Make integration free?
Yes, on the Make side. PostPulse is a standard app, so it is available from the Free plan. That plan allows 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 lower the interval to 1 minute and remove the cap on active scenarios. Your PostPulse subscription is a separate matter, covered by the PostPulse pricing page.
02What do you need to connect PostPulse to Make?
An active PostPulse account and an API key from it. In the scenario, add a PostPulse module, click Create a connection, optionally give the connection a name, then enter the credentials copied from PostPulse or follow the instructions on screen. For an OAuth setup, create an OAuth application in the PostPulse portal with the callback URI given in the Make doc, then copy the Client ID and Client secret into Make.
03Does PostPulse trigger Make scenarios in real time?
No, because PostPulse has no trigger module in Make. All six modules are actions, so the scenario has to start elsewhere. You can open it with a trigger from another app, such as a form or a store, or simply set a schedule on the first module, which is every 15 minutes by default and never under 15 minutes on the Free plan. Paid plans allow a schedule down to 1 minute.
04What if the PostPulse module you need is missing in Make?
Use Make an API call. With this module, any endpoint of the PostPulse API can be called from the scenario, using the same connection as the other modules. Keep in mind that the Make doc for PostPulse is AI-generated from the vendor documentation and may contain mistakes, so check endpoint details with PostPulse directly. For anything that looks wrong, PostPulse support is the right contact. Test any custom request with Run once before switching the scenario on.
05Should you automate PostPulse with Make or n8n?
It depends on the tool your team already runs. On Make, PostPulse brings 6 action modules, Make an API call included, and the scenario starts from another app or a schedule. The same app often has an n8n node as well, so check the node list there before choosing. Pick the platform where your other apps already sit, since one scenario will usually touch them too. Neither is ranked above the other here.
Same platform

Other docs you might need on this stack.

Browse all integrations