Resources · Make integration

FeedHive Make integrationAutomate FeedHive with Make.

Want your other tools to know when a FeedHive post goes live, fails or gets a comment? The FeedHive Make integration gives you 5 modules: 4 scheduled triggers and 1 action. This guide shows social media managers how to connect FeedHive and build a first scenario.

Try the FeedHive integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FeedHive Make integration automate for you?

The FeedHive Make integration links your FeedHive account to Make, the no-code tool where you build a scenario, meaning an automation made of modules placed one after the other. FeedHive brings 4 scheduled triggers that watch your posts and comments, plus 1 action that creates a post from data another app sends.

Catch failures before your audience notices a gap. Watch Failed Post pulls each failed post into Make, and the next module can warn the person who runs your accounts in the tool they already read.

Feed your queue from where ideas start. Drafts often live in a form or a spreadsheet. Create a Post Using Trigger turns each new entry into a FeedHive post, with no copy and paste.

Keep one record of what went out. Watch Published Post logs every published post, and Watch Added Comment brings in the replies, so your reporting starts from a single place.

What Make won't do here: the official doc lists these 5 modules without describing them, and the app has no Make an API Call module, so anything beyond them is out of reach. The doc also warns that its FeedHive page is AI-generated, so test each module with Run once. New to the tool? The Make training starts from zero, Make troubleshooting helps when a scenario misbehaves, and n8n vs Make weighs both tools, since many apps also have an n8n node.

Connect

How do you connect FeedHive to Make?

  1. 01

    Add a FeedHive module

    In your Make account, open a scenario, add any FeedHive module, then click Create a connection. A connection is your FeedHive account linked to Make once, and every FeedHive module reuses it afterwards.

  2. 02

    Copy your API key in FeedHive

    In FeedHive, go to Settings, click Account, then scroll down to the API Key section and copy the key displayed there. This step needs an active FeedHive account.

  3. 03

    Name and save the connection

    Back in Make, fill Connection name if you want a label you will recognize later (it is optional), paste the API key, and follow the on-screen instructions to finish.

First scenario

Build your first FeedHive scenario

GoalWhen a new draft lands in another app, Make creates a post in FeedHive.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. That first module decides when everything starts.

  2. 02

    Start from the app that holds your drafts

    Search the app where drafts get written, such as your spreadsheet or form tool, pick its module and connect that account. Make then lists the sheets or forms it can read.

  3. 03

    Add Create a Post Using Trigger

    Click the + on the right of the first module, search FeedHive, choose Create a Post Using Trigger and select the connection you made earlier.

  4. 04

    Map the draft into the post

    Fill the module by mapping data from the first module, for example the text of the draft. Look at what each field expects on screen, because the doc does not list them.

  5. 05

    Test with Run once

    Add one test draft, then click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can confirm the post reached FeedHive.

  6. 06

    Schedule it and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval allowed.

Triggers

Which FeedHive triggers can start a scenario?

4 modules start a scenario when something happens in FeedHive. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by FeedHive as soon as it happens.

FeedHive1Watch Added Comment

Watch Added Comment

triggerIn the docs only

Watch Added Comment brings each new comment on your FeedHive content into Make as a bundle, one item handed to the next module. You get the comment without opening FeedHive, ready to route to whoever answers your audience.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
when replies are handled by a community manager who works from another tool and needs every comment to land there.
Watch out
the official doc gives no description and no field list for this module, so click Run once on a test post and read the bundle before you map anything.
FeedHive2Watch Failed Post

Watch Failed Post

triggerIn the docs only

This trigger hands Make every FeedHive post that failed, so a publishing error becomes an alert someone actually sees. Without it, a failed post stays quiet until a person opens the calendar.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a failure shows up at the next check rather than the second it happens.
When to use it
when a missed post hurts, such as a launch announcement, and the person in charge should hear about it in the tool they already watch.
Watch out
the doc does not say which errors count as a failure, so confirm with a real failed post before you rely on the alert.
FeedHive3Watch Published Post

Watch Published Post

triggerIn the docs only

Watch Published Post picks up posts once FeedHive has sent them out, which gives you a clean record of what actually went live. Each published post becomes a bundle the next module can log, share or archive.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
when your team keeps a publication log in a spreadsheet, or when sales wants to know which campaign posts are live.
Watch out
it sits right next to Watch Scheduled Post in the module list. Pick by status: published means done, scheduled means still waiting.
FeedHive4Watch Scheduled Post

Watch Scheduled Post

triggerIn the docs only

With Watch Scheduled Post, Make sees the posts waiting in your FeedHive queue before they go out. That gives a reviewer, a manager or a client a chance to read what is coming.

How it fires
scheduled. Make checks the app on the scenario's schedule, so queued posts reach the scenario at the next check.
When to use it
when content gets approved outside FeedHive, in a shared sheet or a team chat, and each queued post should show up there for review.
Watch out
the doc does not say whether an edited post comes back as a new item, so edit a queued post and click Run once to see what happens.
Modules

What can the FeedHive action do?

FeedHive gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

FeedHive1

Create a Post Using Trigger

ActionIn the docs only

Create a Post Using Trigger adds a post to FeedHive from data another module sends, so text written elsewhere reaches your queue. The doc explains nothing beyond the name.

When to use it
when drafts start in another app, such as a spreadsheet row or a form answer, and should end up in FeedHive.
Watch out
no field list is published for it, so open the module once the connection exists and check which fields it asks for before mapping.
Need help

Need help automating FeedHive with Make?

A person reads every message.

FAQ

FeedHive and Make: common questions

01Is the FeedHive Make integration free?
Yes, on the Make side. FeedHive is a standard app, so its 5 modules work on the Free plan. That plan allows 2 active scenarios, scheduled runs at most every 15 minutes, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. FeedHive itself still needs an active account, and that subscription is handled on the FeedHive side, not in Make.
02What do you need to connect FeedHive to Make?
An active FeedHive account and its API key. In FeedHive, open Settings, then Account, and copy the key from the API Key section. In Make, add any FeedHive module, click Create a connection, give it a name if you like, and paste the key. Every FeedHive module then reuses that same connection, so you only set it up once. There is no webhook step to worry about, because none of the 4 FeedHive triggers is instant.
03Do FeedHive triggers in Make fire instantly?
No. All 4 FeedHive triggers are scheduled: Make checks FeedHive on the scenario's schedule, instead of FeedHive calling Make. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is the shortest interval, while paid plans go down to 1 minute. A failed or published post therefore reaches your scenario at the next check. Keep in mind that each module run on a bundle counts as one operation on your plan.
04What if a FeedHive module is missing in Make?
Then the FeedHive app alone won't cover it. It has 5 modules and no Make an API Call module, so there is no generic way to reach other FeedHive features from Make. Two routes remain: build that step with another app's module inside the same scenario, or ask the Hack'celeration team to look at your case. Before either, click Run once on the closest module, because the doc describes none of them and a test shows what each one really returns.
05Should you use Make or n8n for FeedHive?
It depends on the tool your team already runs. On Make, FeedHive offers 5 modules, 4 scheduled triggers and 1 action, all available from the Free plan. Many apps also have an n8n node, but this page covers only the Make side, so check the n8n node list for FeedHive before you choose. Then compare on what matters to you: the modules each tool offers for FeedHive, who will maintain the scenarios, and where your other automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations