Resources · Make integration

Buffer Make integrationAutomate Buffer with Make.

Can Make post to Buffer for you? Yes: the Buffer Make integration gives you 3 action modules to create, edit and delete status updates. This guide is for marketers who already use Buffer and want to connect it, then build a first scenario step by step.

Try the Buffer integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Buffer Make integration do for you?

The Buffer Make integration lets a Make scenario (the automation you build, a chain of modules) write to your Buffer account. It has 3 modules, all actions: one creates a status update in the services you select, one edits it, one deletes it. Make does not watch Buffer, so something else starts the flow.

Turn new content into an update. When an article, a product or a row lands in another app, Create a status update writes the matching update in Buffer, so nobody copies text by hand between tools.

Fix an update when the source changes. A price or a link was corrected upstream? Update a status update rewrites the text in the service you choose, as long as your scenario knows which update to edit.

Pull an update that should not go out. When a product is withdrawn or an event is cancelled, Delete a status update removes it for good. Keep this one for cases you are sure about.

What the integration cannot do: it has no trigger, no search module and no Make an API Call module, so it only acts on Buffer. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains plans, and Make training helps if you are new to scenarios.

Connect

How do you connect Buffer to Make?

  1. 01

    Add a Buffer module

    You need a Buffer account first. In Make, open your scenario, add any Buffer module and click Create a connection. A connection is your Buffer account linked to Make once, then reused by every Buffer module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when a colleague or a second Buffer account joins later. Leave Show advanced settings off unless you have your own Buffer client credentials.

  3. 03

    Save and approve access

    Click Save. If Buffer asks you to sign in and confirm access, do it in the window that opens. Back in Make, the connection appears in the module and you can fill its fields.

First scenario

Build your first scenario with Buffer

GoalWhen new content shows up in another app, Make creates a status update in Buffer.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where your content starts, since Buffer has no trigger of its own.

  2. 02

    Add the Buffer action

    Click the + on the right of that first module, search for Buffer and choose Create a status update. Select your connection or click Create a connection.

  3. 03

    Map the content

    Fill the module fields. Once the connection exists, Make lists what it can read from Buffer, and you drag data from the first module (a title, a link) into the text of the update.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items that moved from one module to the next. Check the new update in Buffer before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Adjust it if your plan allows, then switch the scenario on so it runs without you.

Modules

What the Buffer modules do

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

Buffer1

Create a status update

Action

In Make“Creates a new status update in selected services.”

You get a fresh status update in Buffer for the services you pick, filled with data from earlier modules instead of copied text. Each run on one bundle counts as one operation on your plan.

When to use it
a new blog article or product appears in another tool and should become an update without anyone retyping it.
Watch out
if the first module sends several bundles, Make creates one update per bundle.
Buffer2

Delete a status update

Action

In Make“Permanently removes a status update from a selected service.”

This module takes an update off a service you select, so something that should no longer go out disappears from Buffer without a manual cleanup. The removal is permanent.

When to use it
an offer ends early or an event is cancelled, and the update tied to it must go.
Watch out
there is no undo, so test with Run once on a dummy update before switching the scenario on.
Buffer3

Update a status update

Action

In Make“Edits a status update in a selected service.”

Your existing update gets corrected in the service you choose, instead of being deleted and rebuilt. The text stays in sync with the source when a detail changes.

When to use it
a price, a date or a link was fixed upstream and the planned update still shows the old version.
Watch out
the module edits one specific update, so your scenario must already know which one, for example from an earlier Create a status update run.
Need help

Need help automating Buffer with Make?

A person reads every message.

FAQ

Buffer and Make: frequently asked questions

01Is the Buffer Make integration free?
Yes, Buffer is a standard app, available from the Make Free plan. The Free plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month, and every Buffer module run is one operation. This page gives no price for Buffer itself.
02What do you need to connect Buffer to Make?
A Buffer account and a Make account are enough. Add a Buffer module, click Create a connection, optionally give it a name, then click Save and confirm access in Buffer if asked. Client credentials under Show advanced settings are optional: they only matter if you use your own, and the Buffer documentation explains how to get them. The connection is created once and reused by the three Buffer modules, so you never repeat the setup inside the same scenario.
03Does the Buffer Make integration react in real time?
No, because Buffer has no trigger in Make: none of its 3 modules can start a scenario. Two options remain. Start the scenario with a trigger from another app, the one where your content is created, and let Buffer act second. Or run it on a schedule set on the first module, every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. Either way, Buffer only receives what the scenario sends.
04What if a Buffer module is missing in Make?
It depends on what you need. The Buffer app in Make covers three actions on status updates: create, update and delete. It has no search module, no trigger and no Make an API Call module, so anything beyond those three actions is out of reach with this app alone. Check whether another app in your scenario can supply the missing data, or ask the team to look at your case. The Make documentation lists no numeric limit for Buffer.
05Should you use Make or n8n for Buffer?
It depends on your criteria rather than on a winner. On the Make side, the facts are clear: 3 action modules, a connection in a few clicks and availability from the Free plan, with no trigger. The same app often has an n8n node too, so check what it covers before choosing. Compare the actions each tool offers for Buffer, how your team already works, and which tool already hosts your other automations. Keeping everything in one place is often simpler.
Same platform

Other docs you might need on this stack.

Browse all integrations