Resources · Make integration

PostFast - Social Media Scheduling Make integrationAutomate PostFast - Social Media Scheduling with Make.

Can your social posts land in PostFast without anyone copying them over? The PostFast - Social Media Scheduling Make integration gives you 7 modules: 5 actions and 2 searches. This page walks you through the connection, a first scenario and each module.

Try the PostFast - Social Media Scheduling integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PostFast - Social Media Scheduling Make integration do?

It lets a Make scenario (the automation you build in Make, a chain of modules) write to your PostFast account. A module is one brick of that chain. Here the bricks create posts, create them in batches, delete them, search them and list your connected social accounts, with no code.

Posts that come from somewhere else. A content team writes in a shared tool; another app starts the scenario, and Create a Post drops each approved text into PostFast. List Social Accounts tells the scenario which profile gets it.

A whole campaign at once. When a launch needs several posts, Create a Post Batch sends them together instead of one module run per post. Each run of a module is an operation, the unit Make counts on your plan.

Cleanup after a change of plans. Search Posts finds what is already queued, and Delete a Post removes the entry that no longer fits, for example after a product delay.

Two limits to know. PostFast has no trigger in Make, so the scenario always starts from another app or from a schedule. The official PostFast documentation also warns that it is AI-generated and may contain mistakes, so check anything critical with PostFast. For the wider picture, read the Make review, compare tools with n8n vs Make, or check plans on Make pricing.

Connect

How do you connect PostFast - Social Media Scheduling to Make?

  1. 01

    Generate an API key in PostFast

    Log in to PostFast and open the Workspace Settings page. If no key exists yet, click the button that generates one, then copy the API key shown on screen. Keep it somewhere safe for the next step.

  2. 02

    Add a PostFast module in Make

    In your Make scenario, add any PostFast module and click Create a connection. A connection is your PostFast account linked to Make once, then reused by every PostFast module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the on-screen instructions, and save. Make now reads your PostFast workspace, so the next fields can offer real values instead of asking you to type everything by hand.

First scenario

Build your first scenario with PostFast

GoalWhen a post is approved in another app, Make picks the right social account in PostFast and creates the post there.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the module of the app where your team approves posts: that is where the flow begins, since PostFast has no trigger.

  2. 02

    Add List Social Accounts

    Click the + on the right, search PostFast and choose List Social Accounts. Click Create a connection and paste your API key. This search returns the profiles linked to your workspace.

  3. 03

    Add Create a Post

    Add Create a Post after it. Map the approved text from the first module and the account from the search into its fields, so each post goes to the right profile.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows each bundle, one item passed from module to module. Open them to confirm the post reached PostFast as expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, the shortest interval on the Free plan) and switch the scenario on. From then on, approved posts reach PostFast without copy and paste.

Modules

What each PostFast module does

PostFast - Social Media Scheduling gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PostFast - Social Media Scheduling1

Create a Post

ActionIn the docs only

This action puts one post into your PostFast account from data another module already holds, so nobody retypes the text. You end up with the post waiting in PostFast.

When to use it
a single approved item, such as a blog article just published, should become one social post.
Watch out
the official documentation describes no fields, so check in Make which account and content fields the module asks for before mapping.
PostFast - Social Media Scheduling2

Create a Post Batch

ActionIn the docs only

Here you send several posts to PostFast in one module run, which keeps a campaign together and can save operations compared with one Create a Post per item.

When to use it
a launch plan lives in a sheet and every line should become a post at the same moment.
Watch out
the documentation gives no batch size, so test with Run once on a small set first.
PostFast - Social Media Scheduling3

Delete a Post

ActionIn the docs only

Removing a post from PostFast is the job of this action, handy when a message is no longer accurate before it goes out.

When to use it
a product launch slips and the announcement queued in PostFast has to disappear.
Watch out
a deletion cannot be undone from Make, so place Search Posts before it and check that the bundle points to the right post.
PostFast - Social Media Scheduling4

Get Upload URLs

ActionIn the docs only

Its name suggests this action returns addresses for sending files to PostFast, likely images or videos for a post; no official description confirms it.

When to use it
a post needs media and you want to see what PostFast returns before Create a Post.
Watch out
run it alone with Run once and read the bundle before building a flow on it.
PostFast - Social Media Scheduling5

List Social Accounts

SearchIn the docs only

This search gives your scenario the social profiles connected to the PostFast workspace, so a post can target the right one without guessing.

When to use it
right before Create a Post, when a brand runs several profiles and the scenario must choose.
Watch out
a search returns zero, one or several bundles, and each one can run the next module; filter to the profile you need.
PostFast - Social Media Scheduling6

Make a custom API call

ActionIn the docs only

When the other six modules miss something, this action lets the scenario send its own request to PostFast with the connection you already set up.

When to use it
you know PostFast offers an operation that none of the named modules covers.
Watch out
the Make documentation lists no endpoint, so rely on PostFast's own API documentation and test each call with Run once.
PostFast - Social Media Scheduling7

Search Posts

SearchIn the docs only

Use this search to find posts already stored in PostFast and pass them to later modules, which avoids duplicates and prepares cleanups.

When to use it
before creating a post, to check whether the same announcement is already queued.
Watch out
it can return several bundles, so a Delete a Post placed after it will act on every post found unless you add a filter.
Need help

Need help automating PostFast - Social Media Scheduling with Make?

A person reads every message.

FAQ

Questions about PostFast and Make

01Is the PostFast - Social Media Scheduling Make integration free?
Yes, on the Make side. PostFast is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most and files up to 5 MB, with 512 MB of data transfer. Paid plans drop the interval to 1 minute. You still need your own PostFast subscription, whose pricing is on the PostFast site. If your team runs several scenarios, the paid plans also remove the cap on active scenarios.
02What do you need to connect PostFast to Make?
An active PostFast account with the admin role, because only an admin can generate the API key. Open Workspace Settings in PostFast, generate the key if none exists, and copy it. Then add a PostFast module in Make, click Create a connection, give it a name if you want, and paste the key. The same connection then serves all 7 modules, so the setup happens once. Check in PostFast who holds the admin role before you open Make, it saves a blocked setup.
03Can PostFast start a Make scenario in real time?
No. PostFast has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario on its own. The scenario starts from another app's trigger, for example a form or a content tool, or from Make's schedule, which runs every 15 minutes by default. PostFast modules then act inside that run, creating, searching or deleting posts. If you need a faster start, a paid plan lowers the minimum interval to 1 minute, and an instant trigger from another app can start the run as soon as its event happens.
04What if a PostFast module you need is missing in Make?
It depends on what is missing. PostFast offers Make a custom API call among its 7 modules, which sends your own request with the existing connection, but the Make documentation lists no endpoint, so check PostFast's API documentation first. Keep in mind the official PostFast doc in Make is AI-generated and may contain mistakes. If the need is complex, the team can help you design the scenario. Test each call with Run once before you switch the scenario on.
05Should you use Make or n8n for PostFast?
It depends on your criteria. In Make, PostFast comes with 7 ready modules, 5 actions and 2 searches, reachable from the Free plan with an API key. Many apps also have an n8n node, but check the n8n catalog for PostFast before choosing. Compare the modules each tool offers for posts and accounts, then pick the one where your team already builds its automations. Whichever tool you choose, start with one small scenario and test it with Run once.
Same platform

Other docs you might need on this stack.

Browse all integrations