Resources · Make integration

Postproxy Make integrationAutomate Postproxy with Make.

Can Make create, publish and tidy your Postproxy posts without a line of code? The Postproxy Make integration gives you 15 modules: 10 actions and 5 searches. It suits marketers and ops teams who already work in Postproxy. This page walks you through the connection and a first scenario.

Try the Postproxy integration on Make See the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Postproxy Make integration do for you?

The Postproxy Make integration links your Postproxy account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. A module is one brick of that chain, here an action or a search on your posts, profiles and profile groups. Postproxy has no trigger of its own, so another app or Make's clock starts the flow.

Turn approved content into posts. For a content team, a new row in a spreadsheet or an answer to a form can feed Create a post, so text written elsewhere lands in Postproxy without copy and paste.

Release drafts when the green light comes. When a campaign is approved in your project tool, Publish a draft post sends out the draft you already prepared in Postproxy, and nobody has to remember to click.

See what is lined up. List calendar events and List posts return their results as bundles, one item each, which you can write into a review sheet or post to a team channel.

Make's own documentation for Postproxy is marked as limited: it gives no prerequisites and no description of each module. When a listed module does not cover your need, Make an API call reaches the rest of the Postproxy API with the same connection. The same app may also exist as an n8n node, and the n8n vs Make comparison helps you choose. To learn the editor step by step, see Make training, and check Make pricing before you scale up.

Connect

How do you connect Postproxy to Make?

01
Open the connection window
Add any Postproxy module to your scenario, for example Create a post, then click Create a connection. A connection is your Postproxy account linked to Make once; every Postproxy module in your scenarios reuses it afterwards.
02
Name the connection
Naming it is optional, but it pays off as soon as you handle more than one Postproxy account, say your own brand and a client's. A clear name tells you at a glance which account a module is about to write to.
03
Authorize Make and save
Depending on what Postproxy offers, approve Make on the Postproxy authorization page or paste the key Postproxy gives you. Click Save: the module fields open up, and Make can now list what it reads from your account.

First scenario

Build your first scenario with Postproxy

GoalWhen a new item shows up in another app, Make creates a matching post in Postproxy.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add the first module. Postproxy has no trigger, so pick the app where your content starts, such as a spreadsheet or a form tool.
02
Add Create a post
Click the + on the right of that first module, search Postproxy and pick Create a post. Click Create a connection if your account is not linked yet.
03
Map your content
Fill the module fields by dragging data from the first module into them. Each bundle, meaning each item received, becomes one post, so one new row gives one new post.
04
Test with Run once
Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received, then look for the new post in Postproxy.
05
Schedule and switch it on
Set the schedule on the first module: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Then switch the scenario on and let it work.

Modules

What each Postproxy module does

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

Postproxy1

Create a post

ActionIn the docs only

Create a post turns content prepared somewhere else into a Postproxy post, so nobody retypes a caption. Every bundle that reaches the module produces one new post.

When to use it

a row added to your editorial sheet, or an approved form answer, should become a post without copy and paste.

Watch out

test on a single row first, because a long list coming in gives exactly as many posts.

Postproxy2

Create a profile group

ActionIn the docs only

This module sets up a fresh profile group in Postproxy straight from your scenario, ready to gather the profiles of one brand or one client.

When to use it

a new client is marked as signed in your CRM and you want their Postproxy space prepared at the same moment.

Watch out

to avoid two groups for the same client, look it up first with List profile groups and add a filter before this module.

Postproxy3

Delete a post

ActionIn the docs only

Delete a post removes one post from Postproxy, which keeps your posts in line with decisions made in other tools.

When to use it

a campaign is cancelled in your project board and its posts should vanish from Postproxy as well.

Watch out

a deletion does not come back. Feed the module the exact post found by Get post or List posts, and rehearse on a dummy post with Run once.

Postproxy4

Delete a profile

ActionIn the docs only

Removing a profile you no longer manage takes one step with this module, and the account stops cluttering your Postproxy workspace.

When to use it

a client contract ends in your CRM and the profile you ran for them has to go.

Watch out

this is permanent, so confirm the target with Get a profile in the step just before, and keep a filter that stops the flow when the name does not match.

Postproxy5

Delete a profile group

ActionIn the docs only

With Delete a profile group, a whole group disappears from Postproxy in one operation, meaning one run of one module, the unit Make counts on your plan.

When to use it

you close a client account for good and want its group gone along with it.

Watch out

a group is wider than a single profile. Read it with Get a profile group first and try the module on an empty test group.

Postproxy6

Get a profile

ActionIn the docs only

Get a profile brings back what Postproxy holds on one profile, so the modules that follow can reuse those details instead of guessing.

When to use it

before you post or delete, you want proof that the scenario aims at the right account.

Watch out

it reads one profile you already know. If you only have a name to start from, find the profile with List profiles first.

Postproxy7

Get a profile group

ActionIn the docs only

Reading a single profile group back from Postproxy is the job here, which gives later modules solid data about that group.

When to use it

you want to check a group before deleting it, or copy its details into a client report.

Watch out

the module expects one specific group. When you are not sure which one, List profile groups returns them all and lets you filter.

Postproxy8

Get post

ActionIn the docs only

Get post fetches one post from Postproxy so you can see what it holds and pass it along to the next module.

When to use it

right after Create a post, to confirm the post exists and log it in your tracking sheet.

Watch out

it returns a single post. To look at many posts at once, switch to List posts, which is a search module.

Postproxy9

List calendar events

SearchIn the docs only

This search hands you the events of your Postproxy calendar, each one as its own bundle, so the whole plan can travel to another tool.

When to use it

your team reviews upcoming content in a shared sheet or a chat channel rather than inside Postproxy.

Watch out

a search can return zero, one or many bundles. Add an aggregator, the module that groups bundles, if you want one message instead of one per event.

Postproxy10

List posts

SearchIn the docs only

List posts returns your Postproxy posts as separate bundles, which makes reports and cleanups possible without opening the app.

When to use it

you want to find the posts of a cancelled campaign before sending them to Delete a post.

Watch out

every bundle runs the next modules once, and each run counts as an operation, so narrow the result with a filter early.

Postproxy11

List profile groups

SearchIn the docs only

You get every profile group in your Postproxy account from this search, one bundle per group, ready to compare with your client list.

When to use it

before Create a profile group, to check whether the client already has one.

Watch out

the result can be empty. Plan what the scenario should do in that case rather than assume a group always comes back.

Postproxy12

List profile placements

SearchIn the docs only

List profile placements returns the placements Postproxy keeps for your profiles, as bundles you can pass to later modules.

When to use it

you need to read those placements before a posting step decides where content goes.

Watch out

Make's documentation does not describe what a placement contains, so click Run once and read the bundles before you build anything on top of them.

Postproxy13

List profiles

SearchIn the docs only

Every profile connected to your Postproxy account comes back from this search, each one as a bundle you can filter or map.

When to use it

a scenario has to pick the right profile by name before it creates or deletes anything.

Watch out

with many profiles, the modules after it run once per bundle, so filter on the name you need right after the search.

Postproxy14

Make an API call

ActionIn the docs only

Make an API call lets you reach any endpoint of the Postproxy API from your scenario, reusing the connection you already created.

When to use it

you need something Postproxy offers that none of the other listed modules covers.

Watch out

Make's documentation for Postproxy is limited and does not describe the API, so you write the request yourself: test it with Run once first.

Postproxy15

Publish a draft post

ActionIn the docs only

Publish a draft post takes a draft sitting in Postproxy and sends it out, so approval in one tool can trigger publication in another.

When to use it

a manager ticks the approved box in your project board and the matching draft should go live.

Watch out

once published, the post is in front of your audience, so rehearse the scenario on a harmless draft first.

Need help

Need help automating Postproxy with Make?

A person reads every message.

FAQ

Postproxy and Make: common questions

01Is the Postproxy Make integration free?

Yes, Postproxy is a standard app in Make, so it works from the Free plan onward. 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. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run, every month.

02What do you need to connect Postproxy to Make?

A Postproxy account and a Make account are enough, since Make's documentation lists no other prerequisite. Add any Postproxy module, click Create a connection, give it a name if you like, then either approve Make on the Postproxy authorization page or paste the key Postproxy provides. Click Save and the connection is ready. Every Postproxy module in your scenarios reuses it, so you only do this once per account, even across many scenarios.

03Can Postproxy start a Make scenario in real time?

No, because Postproxy has no trigger module in Make. You start the scenario another way. The first option is a trigger from another app, a spreadsheet or a form for example, followed by Postproxy modules. The second is the schedule on the first module: a new scenario runs every 15 minutes by default, which is also the Free plan minimum, while paid plans go down to 1 minute. For a trigger that reacts instantly, that other app needs an instant trigger of its own.

04What if a Postproxy module you need is missing in Make?

Use Make an API call. It reaches any endpoint of the Postproxy API from your scenario with the same connection, so you are not limited to the 15 listed modules. Keep in mind that Make's documentation for Postproxy is marked as limited: it describes neither the modules nor the API in detail. You write the request yourself, so test each call with Run once and read the bundles before switching the scenario on.

05Should you use Make or n8n for Postproxy?

It depends on the tool your team already uses. In Make, Postproxy offers 15 modules, 10 actions and 5 searches, plus Make an API call for everything else, and it runs from the Free plan. The same app often has an n8n node as well, so check that it exists and covers the actions you need before choosing. Neither tool is ranked here: compare the modules each one gives you for Postproxy, then pick the editor your team is comfortable building in.

Open the connection window

Name the connection

Authorize Make and save

Create the scenario

Add Create a post

Map your content

Test with Run once

Schedule and switch it on

Need help automating Postproxy with Make?