Resources · Make integration

Metricool Make integrationAutomate Metricool with Make.

What if your posts reached Metricool's planner without anyone copying them over? The Metricool Make integration gives you 7 modules: 2 actions and 5 searches. It suits marketers and social media managers who already run Metricool, and this guide takes you from the connection to a first working scenario.

Try the Metricool integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Metricool Make integration do for you?

The Metricool Make integration links your Metricool account to Make so a scenario, the automation you build in Make, can put posts into the planner and read back what happened to them. Each step of that scenario is a module, one brick that either acts in Metricool or searches it and hands the results to the next brick.

A planner fed from your content calendar. Your team writes captions in a table; when a row is ready, Schedule a Post queues it in Metricool. If your calendar lives in Airtable, the Airtable Make integration explains the other half of that flow.

No silent publishing failures. List Failed Posts returns the posts that did not go out, so a scenario can post them to your team chat or open a task before the campaign loses its slot.

Numbers where your reports already live. Get Network Metrics pulls your network figures so you can write them into a spreadsheet or a client dashboard instead of exporting them by hand.

Know the limits before you start. Metricool offers no trigger in Make, so a scenario never starts because something happened in Metricool: it runs on a schedule or after another app's trigger. You also need a paid Metricool account to connect. For a wider view of the tool, read our Make review, and if you are weighing another platform, the n8n vs Make comparison sets out the criteria.

Connect

How do you connect Metricool to Make?

  1. 01

    Copy your API key in Metricool

    Log in to Metricool, open the Menu icon in the upper-right corner, then Account settings and API. Copy the API Key value and keep it somewhere safe, since anyone holding it can reach your account.

  2. 02

    Add a Metricool module in Make

    In your scenario, add any Metricool module and click Create a connection. A connection is your Metricool account linked to Make once; every Metricool module of your scenarios reuses it afterwards.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you manage several brands, paste the key into API Key and click Save. If Make asks you to authenticate and confirm access, accept and you are ready.

First scenario

Build your first scenario with Metricool

GoalWhen a new post is ready in another app, Make queues it in Metricool's planner.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Metricool has no trigger, so the first module comes from the app where your posts are written, a table or a form for example.

  2. 02

    Set up the starting module

    Pick that app, create its connection and fill its fields. Each item it returns is a bundle: one post idea that travels to the next module with its text and details.

  3. 03

    Add Schedule a Post

    Click the + on the right, search for Metricool and choose Schedule a Post. Select your connection, then map the caption and details from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once and open the bubbles above each module to read the bundles it received. Then check the Metricool planner: the test post should be waiting there.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as an operation on your Make plan.

Modules

What can the Metricool modules do?

Metricool gives you 7 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

2 modules
Metricool1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Metricool API from your scenario, using the connection you already set up, so you are not stuck when the six other modules stop short of your need.

When to use it
a task the listed modules do not cover, once you have found the matching call in Metricool's API documentation.
Watch out
you write the request yourself, so test it with Run once before letting it touch live posts.
Metricool2

Schedule a Post

Action

In Make“Schedule a new post using Metricool's planner.”

Places a new post in Metricool's planner, which means a caption approved elsewhere reaches your publishing queue without anyone pasting it in by hand.

When to use it
right after a post is validated in your content table, your form or your approval flow.
Watch out
this module acts on each bundle it receives, so a search upstream that returns several rows will schedule several posts; filter before it.

Searches

5 modules
Metricool3

Get Network Metrics

Search

In Make“Retrieves metrics from networks.”

Brings back the metrics Metricool holds for your networks, giving your reporting a direct source instead of a manual export from the dashboard.

When to use it
when a client report or an internal dashboard needs fresh figures written into a sheet or a document.
Watch out
as a search, it can return several bundles, so plan an aggregator if the next module expects a single row.
Metricool4

List Draft Posts

Search

In Make“List draft posts.”

Returns the posts still sitting as drafts in Metricool, so a forgotten caption surfaces before its publishing window closes.

When to use it
to send your editor a digest of what is waiting for approval, or to push drafts into a review board.
Watch out
an empty result is normal when nothing is pending; add a filter so the scenario does not send an empty message.
Metricool5

List Failed Posts

Search

In Make“List failed posts.”

Gives you the posts Metricool could not publish, which is the quickest way to catch a broken campaign before your audience notices the gap.

When to use it
in a scenario that alerts the person on duty through chat or email whenever this search finds something.
Watch out
the module only lists failures; fixing and rescheduling each post remains a separate step, in Metricool or with Schedule a Post.
Metricool6

List Published Posts

Search

In Make“List published posts on your networks.”

Collects the posts already live on your networks, handy for keeping a clean archive of what actually went out, outside of Metricool.

When to use it
to log each published post in a spreadsheet or a CRM, next to the campaign it belongs to.
Watch out
the same post comes back on every run, so store an identifier and skip the ones you already logged.
Metricool7

List Scheduled Posts

Search

In Make“List scheduled posts.”

Shows everything queued in the planner and not yet published, so your team can review the coming schedule without opening Metricool.

When to use it
before a launch, to share the upcoming posts with a client or a manager for a last check.
Watch out
it reads the queue but changes nothing in it; editing a scheduled post still happens in Metricool.
Need help

Need help automating Metricool with Make?

A person reads every message.

FAQ

Metricool and Make: frequent questions

01Is the Metricool Make integration free?
On the Make side, yes: Metricool is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. On the Metricool side, the connection requires a paid Metricool account, so the integration is never entirely free. Keep in mind that each module run on one bundle counts as one operation on your Make plan.
02What do you need to connect Metricool to Make?
A paid Metricool account and its API key. In Metricool, open the Menu icon, then Account settings and API, and copy the API Key value. In Make, add a Metricool module, click Create a connection, paste the key into the API Key field and click Save. If Make asks you to authenticate, confirm access. The connection is then reused by every Metricool module in your scenarios. Give the connection a clear name if you handle several brands, since you pick it by that name in every module.
03Can a Metricool Make scenario react in real time?
No. Metricool has no trigger in Make, neither scheduled nor instant, so nothing in Metricool can start a scenario by itself. You start it another way: with the schedule on the first module, every 15 minutes by default, or with a trigger from another app, such as a new row in your content table. The Metricool modules then run as actions and searches inside that flow. Before switching on, click Run once to check what each Metricool module returns.
04What if the Metricool module you need is missing in Make?
Use Make an API Call. It lets a scenario call any endpoint of the Metricool API with the connection you already created, which covers what the six other modules leave out. You write the request yourself from Metricool's API documentation, so test it with Run once before switching the scenario on. The Metricool documentation for Make lists no specific limits. If you are unsure, start from the list of 7 modules first and keep the API call for what remains.
05Should you pick Make or n8n for Metricool?
It depends on what the rest of your stack runs on. In Make, Metricool comes with 7 ready modules to schedule posts, list drafts, failures, published and scheduled posts, and read network metrics, plus Make an API Call for the rest. If your other automations already live in n8n, check whether a Metricool node exists there before choosing. The comparison page linked above lays out the criteria side by side. Both tools can call an API, so the gap usually comes down to habits and the tools around it.
Same platform

Other docs you might need on this stack.

Browse all integrations