- Home
- Resources
- Integrations
- PostPeer
PostPeer Make integrationAutomate PostPeer with Make.
Can Make create your PostPeer posts for you? Yes. The PostPeer Make integration gives you 2 action modules, one to create a post and one to call the API. This page shows how to link your account and build a first scenario step by step.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PostPeer Make integration let you automate?
The PostPeer Make integration links your PostPeer account to Make so a post can be created without opening PostPeer. You build a scenario, which is the automation itself: a chain of modules, each module being one brick from one app. PostPeer brings two action bricks, and something else has to start the chain.
Posts that follow your content. A new row in a spreadsheet, a form answer or a message in another tool can start the scenario, and the Create a post module turns that data into a PostPeer post. Each item passed along is called a bundle, and every module run on it is an operation, the unit Make counts on your plan.
Anything the listed module leaves out. The Make an API call module reuses the same connection to reach any endpoint of the PostPeer API, which is how you cover a need the Create a post module does not.
What to keep in mind. PostPeer has no trigger in Make, so it cannot start a scenario on its own. The official documentation is also limited, because little public information exists about the app: expect to discover field names inside the editor. The Make troubleshooting guide helps when a run fails.
PostPeer may also have an n8n node. If you are weighing both tools, the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from zero.
How do you connect PostPeer to Make?
- 01
Add a PostPeer module
In your scenario, add the Create a post module and click Create a connection. A connection is your PostPeer account linked to Make once, then reused by both PostPeer modules.
- 02
Name the connection
Giving it a name is optional, but it helps a lot when several people or several PostPeer accounts share the same Make organization. Something like the account owner or the brand works well.
- 03
Authorize and save
Depending on what PostPeer offers, either approve Make on the PostPeer page that opens or paste the key PostPeer gives you. Then click Save and the module is ready to fill.
Your first scenario with PostPeer
GoalWhen new content lands in another app, Make creates a matching post in PostPeer.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + to add the first module. It will be the app where your content starts, since PostPeer has no trigger.
- 02
Set the starting module
Pick the app that holds your content, connect it and fill its fields. Make lists the sheets, folders or objects it can read once that connection exists.
- 03
Add Create a post
Click the + on the right of the first module, search PostPeer, choose Create a post and connect your account. Map the data from the first module into the post fields.
- 04
Test with Run once
Click Run once to execute the scenario one time. Then read the bundles each module received and check the post looks right in PostPeer.
- 05
Schedule and switch on
On the first module, set the schedule, which is every 15 minutes by default, then switch the scenario on. Make now checks the source app at that interval.
What can the PostPeer modules do?
PostPeer gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a post
ActionIn the docs onlyThis module creates a new post in your PostPeer account from data that another module handed over, so your content reaches PostPeer without copy and paste.
Make an API call
ActionIn the docs onlyReach any endpoint of the PostPeer API from your scenario, reusing the connection you already created, for the cases the Create a post module does not handle.
Need help automating PostPeer with Make?
A person reads every message.