Resources · Make integration

Hive Make integrationAutomate Hive with Make.

Can Make keep your Hive actions and projects moving without you copying things by hand? The Hive Make integration gives you 14 modules: 2 triggers, 10 actions and 2 searches. This guide connects your account, builds a first scenario with you and explains when each module fits.

Try the Hive integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hive Make integration automate?

The Hive Make integration links your Hive workspace to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Hive modules can spot new or edited actions, create and edit actions and projects, post messages and fetch lists, so the busywork between Hive and your other tools runs by itself.

Announce new work to the team. Watch Created Actions picks up each action added in Hive, and Create a Message posts a note about it, so nobody has to ping a colleague about a task that just landed on their plate.

Open projects from another tool. When a deal is signed in your CRM, a scenario can run Create a Project and then Create an Action for the kickoff step. For the CRM side, the Agile CRM Make integration shows how that half works.

Keep two tools in step. Watch Updated Actions notices edits, and Update an Action or Update a Project writes changes back when the other system is the reference. List Actions and List Projects pull a whole workspace when you need a snapshot for a report.

What Make will not do here: both triggers are scheduled, so Make checks Hive on the scenario's schedule instead of hearing from Hive the moment something changes. The Hive documentation in Make also warns that it is AI-generated from the vendor's docs and may contain mistakes, so test before relying on it. If a module is missing, Make an API Call reaches the rest of the Hive API with the same connection.

Hive may also have a node in n8n. The n8n vs Make comparison lays out the criteria, and the Make training helps if you want to build these scenarios yourself.

Connect

How do you connect your Hive account to Make?

  1. 01

    Copy your Hive API key

    In Hive, open the main menu in the top-right corner, select My profile, then the API info tab. Generate a new API key and copy the value shown on screen. You need an active Hive account for this.

  2. 02

    Create the connection in Make

    Add any Hive module to your scenario and click Create a connection. A connection is your Hive account linked to Make once, then reused by every Hive module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Hive into the field Make shows and save. From then on, Make can read and write in your workspace, and every other Hive module in the scenario picks the same connection from a dropdown.

First scenario

Build your first scenario with Hive

GoalWhen a new action is created in Hive, Make posts a message about it in Hive.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to add the first module of the chain.

  2. 02

    Add the Hive trigger

    Search for Hive, pick Watch Created Actions and choose your connection. Make lists what it can read in your workspace once the connection exists, so you pick instead of typing.

  3. 03

    Add the message

    Click the + on the right of the trigger, add Create a Message and map the action's details from the trigger into the message, so each post names the new action.

  4. 04

    Test with Run once

    Create a test action in Hive, then click Run once. Open the bubble above each module to read the bundles it received: a bundle is one item passed along, here one action.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks Hive (every 15 minutes by default), then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts a Hive scenario

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

Hive1Watch Created Actions

Watch Created Actions

Scheduled trigger

In Make“Triggers when an action is created.”

Starts your scenario with every action that appears in Hive, handing each one to the next module as its own bundle. It is the natural entry point when new work should set something in motion elsewhere.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule and collects the actions created since the last check.
When to use it
a new action needs to be announced, copied into another tool or logged in a sheet the moment it is picked up.
Watch out
edits to existing actions do not start this trigger; that is the job of Watch Updated Actions.
Hive2Watch Updated Actions

Watch Updated Actions

Scheduled trigger

In Make“Triggers when an action is updated.”

Reacts to changes rather than to new work: each action that was edited in Hive reaches your scenario, so another tool can follow what moved without anyone reporting it by hand.

How it fires
scheduled as well, Make checks the app on the scenario's schedule, so an edit shows up at the next run and not the second it happens.
When to use it
a client portal, a spreadsheet or a second project tool must reflect what the team changes in Hive.
Watch out
if your scenario writes back to Hive with Update an Action, that write will most likely count as an update too; filter those runs out so the scenario does not keep feeding itself.
Modules

Every Hive module in Make

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

Hive1

Create a Message

Action

In Make“Creates a new message.”

Posts a new message in Hive from your scenario, which turns events from any tool into a line your team reads where it already works. It is the module to reach for when the goal is telling people, not changing tasks.

When to use it
a form is submitted or an action is created, and the team should hear about it inside Hive.
Watch out
map real details from earlier modules, or every message will read the same.
Hive2

Create an Action

Action

In Make“Creates a new action.”

Adds a new action to Hive, filled with data mapped from earlier modules, so work that starts in an email, a form or a CRM lands straight on the team's plate.

When to use it
a request arrives outside Hive and someone must act on it; this saves retyping it.
Watch out
if the same request can arrive twice, search first with List Actions, or you will end up with duplicates.
Hive3

Create a Project

Action

In Make“Creates a new project.”

Opens a fresh project in Hive at the moment something upstream says a new piece of work begins, such as a signed deal or an accepted quote.

When to use it
every new client or engagement gets its own project, and you want it ready before kickoff.
Watch out
chain Create an Action right after it when the project should start with a first task, rather than leaving it empty.
Hive4

Delete an Action

Action

In Make“Deletes an action.”

Removes an action from Hive, which keeps a workspace clean when a request is withdrawn or duplicated in another system.

When to use it
a ticket is cancelled in the source tool and its twin in Hive should disappear too.
Watch out
treat a deletion as final: test on a dummy action with Run once and add a filter before the module so only the right actions reach it.
Hive5

Delete a Project

Action

In Make“Deletes a project.”

Deletes a whole project in Hive, the heavier cousin of Delete an Action, meant for closing down work that should leave no trace in the workspace.

When to use it
a test project or a deal that fell through was created automatically and must go.
Watch out
treat it as final, so place a filter in front and check with Get a Project that you hold the right one before deleting.
Hive6

Get an Action

Action

In Make“Gets an action.”

Fetches one action you already know, so later modules work with its full details instead of the few a trigger or a list returned.

When to use it
you have the action's identifier from an earlier step and need the rest of its data before writing a message or a report line.
Watch out
it reads a single action; to browse a workspace, List Actions is the right module.
Hive7

Get a Project

Action

In Make“Gets a project.”

Reads one project from Hive so the scenario can use its details, for instance to name the project in a message or copy it into a report.

When to use it
an earlier step gives you the project to look up, and you want the project's information next to it.
Watch out
it needs to know which project to fetch; if you only have a name, start from List Projects instead.
Hive8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request of your own to the Hive API, using the connection you already set up, so you can reach anything the ready-made modules do not cover.

When to use it
you need a Hive feature that has no module in this list and the Hive API documentation describes the endpoint.
Watch out
you write the request and read the raw response yourself, which asks for more care than a regular module.
Hive9

Update an Action

Action

In Make“Updates an action.”

Changes an existing action in Hive with data from the scenario, so a status or detail edited in another tool is reflected without a manual copy.

When to use it
the other system is the reference, and Hive should follow when something changes there.
Watch out
paired with Watch Updated Actions on the same actions, each write is likely to count as a new update, so add a filter to stop the scenario from looping.
Hive10

Update a Project

Action

In Make“Updates a project.”

Edits a project that already exists in Hive, handy when a client, a budget line or a deadline changes in the tool where your sales or finance team works.

When to use it
project details live in a CRM or a spreadsheet first and Hive should mirror them.
Watch out
you need the project's identifier; find it with List Projects or Get a Project in an earlier step.
Hive11

List Actions

Search

In Make“Gets all actions for a given workspace.”

Returns all actions of a given workspace, each one as its own bundle, which makes it the tool for audits, exports and duplicate checks.

When to use it
you want a full picture of the actions in a workspace, or you must check whether one exists before creating it.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations fast.
Hive12

List Projects

Search

In Make“Gets all projects for a given workspace.”

Gathers every project in a workspace and passes them on one by one, useful to build a portfolio report or to find the project an automation should touch.

When to use it
you know a project's name but not its identifier, or you want all projects copied to a sheet.
Watch out
when nothing matches, the modules after it simply do not run, so check the bundles with Run once before switching on.
Need help

Need help automating Hive with Make?

A person reads every message.

FAQ

Hive and Make: common questions

01Is the Hive Make integration free?
Yes, Hive is a standard app, so it works on the Make Free plan. That plan caps you at 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops each run after 5 minutes and allows 512 MB of data transfer. Paid plans go down to a 1 minute interval and count usage in credits. You still need your own Hive account to generate the API key.
02What do you need to connect Hive to Make?
An active Hive account and an API key. In Hive, open the main menu at the top right, open your profile, then the API info tab, and generate a key. In Make, add a Hive module, click Create a connection, optionally give it a name, and paste the key. That single connection then serves all 14 Hive modules in your scenarios. If you manage several Hive accounts, create one connection per account and give each a clear name.
03Does the Hive trigger in Make work in real time?
No. Watch Created Actions and Watch Updated Actions are both scheduled triggers: Make checks Hive on the scenario's schedule, every 15 minutes by default. On a paid plan you can shorten the interval to 1 minute. Hive has no instant trigger in Make, so if you need faster reactions, look at running the scenario more often rather than expecting a push from Hive. You set that rhythm with the clock on the first module, and Run once lets you test the scenario right away without waiting for the next scheduled check.
04What if a Hive module is missing in Make?
Use Make an API Call. It calls any endpoint of the Hive API with the connection you already created, so features without a dedicated module stay within reach. Keep in mind that the Hive documentation inside Make is AI-generated from the vendor's docs and may contain mistakes; test each call with Run once and check with Hive directly when something looks off. For everyday needs, the other modules already cover creating, reading, updating and deleting actions and projects, plus messages.
05Should you use Make or n8n for Hive?
It depends on the tool your team already uses. Many apps also have an n8n node, so check whether Hive does before choosing. In Make you get 14 ready modules, a visual editor and a free plan to start with 2 active scenarios. Compare how each tool fits your other apps and your team's habits before deciding, rather than looking for a winner. A short test with Run once on the Free plan is a simple way to see whether the Make side suits your team.
Same platform

Other docs you might need on this stack.

Browse all integrations