Resources · Make integration

Gmelius Make integrationAutomate Gmelius with Make.

Can Make handle your shared inbox work in Gmelius? The Gmelius Make integration gives you 14 modules: 2 instant triggers, 10 actions and 2 searches. This guide connects your account, builds a first scenario and explains when each module is worth picking.

Try the Gmelius integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Gmelius Make integration automate?

The Gmelius Make integration links your Gmelius account to Make, a tool where you build automations called scenarios without writing code. A scenario is a chain of modules, and each module is one brick: a trigger that starts things, an action that changes something, or a search that fetches items.

Every new conversation gets an owner. Watch Conversation Created fires the moment a conversation lands, and Assign a Conversation hands it to the right teammate. Add Create a Note on a Conversation to leave context for whoever picks it up.

Board changes reach the rest of your stack. Watch Board Updated tells Make when a board you follow changes. Get a Board then pulls its details so another app, a spreadsheet or a chat tool, can show the update to people who never open Gmelius.

Boards created from other apps. When a project starts in your CRM or form tool, Create a Board opens the matching board in Gmelius, and Update a Board keeps it in line when the project changes. List Boards helps you check what already exists before creating a duplicate.

The listed modules do not cover the whole Gmelius API. Make an API Call fills that gap with the same connection. You also need a Gmelius Growth or Enterprise plan, and only admins and managers can get the API credentials. Unsure whether Make suits your team? Read the Make review, or compare both tools in n8n vs Make. If you would rather have the build done for you, the Make agency team can take it on.

Connect

How do you connect Gmelius to Make?

  1. 01

    Grab your API credentials in Gmelius

    Log in to Gmelius, open your account page and go to the API credentials section. If Gmelius asks for a callback URI, paste https://www.integromat.com/oauth/cb/gmelius. Copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a Gmelius module in Make

    In your Make scenario, click the +, search for Gmelius and pick any module. Then click Create a connection. A connection is your Gmelius account linked to Make once, then reused by every Gmelius module you add later.

  3. 03

    Name the connection and authorize

    The Connection name field is optional, but a clear name helps when several people share the scenario. Paste the credentials you copied from Gmelius, or follow the on-screen instructions, and save. Make can now read your boards and conversations.

First scenario

Your first scenario: assign every new Gmelius conversation

GoalWhen a new conversation is created in Gmelius, Make assigns it to the teammate you picked.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to add the first module. That first module decides when everything else runs.

  2. 02

    Add the Gmelius trigger

    Search for Gmelius and choose Watch Conversation Created. Click Create a webhook, then Create a connection with the credentials from your Gmelius account.

  3. 03

    Add the assignment

    Click the + on the right of the trigger and pick Assign a Conversation. Map the conversation coming from the trigger, then fill the other fields with the options Make lists for your account.

  4. 04

    Test it with Run once

    Click Run once, then create a test conversation in Gmelius. Open each module's bubble to read the bundle it received, meaning the single conversation that flowed through, and check the assignment in Gmelius.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because the trigger is instant, Gmelius calls Make as soon as a conversation is created, so there is no polling schedule to tune on this first module.

Triggers

What can start a Gmelius scenario?

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

Gmelius1Watch Board Updated

Watch Board Updated

Instant trigger

In Make“Triggers when the selected board is updated.”

Watch Board Updated starts your scenario whenever the board you selected changes, so the people outside Gmelius hear about it without checking the board themselves. You pick one board when you set up the module, and every update to it becomes a bundle, one item passed to the next module.

How it fires
instant. Gmelius calls Make through a webhook as soon as the board is updated, which shows as the lightning badge on the module.
When to use it
a client project board where a manager wants a message in the team chat each time the board moves.
Watch out
it follows the selected board only, so a second board needs its own scenario or its own trigger.
Gmelius2Watch Conversation Created

Watch Conversation Created

Instant trigger

In Make“Triggers when a new conversation is created.”

Watch Conversation Created gives you a scenario that reacts to every new conversation in Gmelius, which is the natural starting point for routing, tagging or logging your shared inbox. Each new conversation arrives in Make as one bundle you can pass to the next modules.

How it fires
instant. Gmelius calls Make through a webhook as soon as the conversation is created, no waiting for a polling interval.
When to use it
a support or sales inbox where each incoming request must get an owner and a note before anyone replies.
Watch out
set it up with Create a webhook before Create a connection, or the trigger has nothing to listen on.
Modules

What can Make do in Gmelius?

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

Gmelius1

Assign a Conversation

Action

In Make“Assigns the selected conversation.”

Assign a Conversation gives a conversation an owner without anyone opening Gmelius to drag it across. Make sets the assignment from data it already has, like the conversation that just arrived or the result of a search.

When to use it
right after Watch Conversation Created, to route a request by the sender or topic you read upstream.
Watch out
it acts on one conversation per run, so feed it a single bundle, not a whole list.
Gmelius2

Create a Board

Action

In Make“Creates a new board.”

Create a Board opens a new board in Gmelius from an event that happens somewhere else, so a fresh project already has its space when the team gets to it. It saves the manual setup each time a deal closes or a form comes in.

When to use it
a won deal in your CRM that should become a client board straight away.
Watch out
nothing stops a second run from creating a twin board; check with List Boards first if the event can repeat.
Gmelius3

Create a Note on a Conversation

Action

In Make“Creates a note on the selected conversation.”

Create a Note on a Conversation leaves context on a thread for your teammates, not for the customer. It is how you bring data from another app, an order status or an account owner, right into the conversation where people work.

When to use it
after a new conversation arrives, to add what your CRM knows about the sender.
Watch out
pick Reply to a Conversation instead when the text is meant for the person who wrote in.
Gmelius4

Delete a Board

Action

In Make“Deletes the selected board.”

Delete a Board removes the board you select, which keeps Gmelius tidy when projects close in another tool. It is the cleanup step at the end of a flow, not something to place at the start.

When to use it
a project marked as cancelled in your project tool, whose board no longer has a reason to exist.
Watch out
a deletion is not something Make can undo, so test it on a spare board with Run once before switching the scenario on.
Gmelius5

Get a Board

Action

In Make“Returns information about the selected board.”

Get a Board returns the details of one board so later modules can use them. On its own it changes nothing; its value is in feeding a message, a report row or a decision further down the scenario.

When to use it
after Watch Board Updated, to pull the full board before posting a summary in your chat tool.
Watch out
it reads one board you point it to; to go through all of them, start with List Boards.
Gmelius6

Get a Conversation

Action

In Make“Returns information about the selected conversation.”

Get a Conversation fetches everything Make can read about one conversation, handy when an earlier module only handed you a reference. With the details in hand, the next modules can route, log or reply with the right context.

When to use it
when the next module needs the full thread, for example to write a note that sums up the request.
Watch out
each call counts as an operation, one module run that Make bills against your plan, so skip it when the trigger already carries what you need.
Gmelius7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any part of the Gmelius API that the listed modules leave out, using the connection you already created. It is the fallback that saves you from switching tools when one action is missing.

When to use it
a Gmelius feature your team relies on that no other module on this page covers.
Watch out
you write the request yourself, so keep the Gmelius API documentation open while you set it up.
Gmelius8

Reply to a Conversation

Action

In Make“Replies to the selected conversation.”

Reply to a Conversation sends an answer on the thread itself, so the person who wrote in hears back without anyone typing it. It works well for acknowledgments and standard answers built from data Make collected.

When to use it
a request form where every new ticket gets a first reply confirming it was received.
Watch out
the customer sees this text, so run it once on a test conversation and read the result before going live.
Gmelius9

Update a Board

Action

In Make“Updates the selected board.”

Update a Board changes an existing board so it stays in line with the source of truth in another app. You avoid the drift that appears when the same project lives in two tools and only one of them gets edited.

When to use it
a project that changes in your CRM and should look the same in Gmelius.
Watch out
it needs the board to already exist; pair it with List Boards or Get a Board to target the right one.
Gmelius10

Update a Status of a Conversation

Action

In Make“Updates a status of the selected conversation.”

Update a Status of a Conversation moves a thread forward without a manual click, so your inbox reflects what really happened in other tools. A paid invoice or a closed ticket elsewhere can update the matching conversation here.

When to use it
after Reply to a Conversation, to mark the thread as handled once the automatic answer went out.
Watch out
use it on one conversation per run and double check the target, since a wrong status misleads your team about that thread.
Gmelius11

List Boards

Search

In Make“Lists all boards.”

List Boards brings back every board as separate bundles, one per board, which lets the next modules work through them one by one. It is also the simplest way to find the board you want to update.

When to use it
before Create a Board, to check whether a board with that client name already exists.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per board found.
Gmelius12

List Conversations of a Shared Folder

Search

In Make“Lists all conversations of the selected shared folder.”

List Conversations of a Shared Folder returns the conversations of the shared folder you choose, each as its own bundle. It gives you a way to process a backlog, not just the conversations that arrive from now on.

When to use it
a shared folder full of unassigned requests that you want to assign or annotate in one pass.
Watch out
each conversation found triggers the following modules, so a large folder uses more operations than you might expect.
Need help

Need help automating Gmelius with Make?

A person reads every message.

FAQ

Gmelius and Make: common questions

01Is the Gmelius Make integration free?
Yes, on the Make side. Gmelius is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. The catch sits on the Gmelius side: the connection needs a Gmelius account on a Growth or Enterprise plan.
02What do you need to connect Gmelius to Make?
Three things. A Gmelius account on a Growth or Enterprise plan, a role of admin or manager, since only those users can see the API credentials, and a Make account. In Gmelius, open your account page, find the API credentials section, enter the callback URI if asked, then copy the Client ID and Client secret. In Make, add a Gmelius module, click Create a connection and paste both values. Save the connection once and every Gmelius module reuses it.
03Do the Gmelius triggers in Make work in real time?
Yes. Both Gmelius triggers, Watch Board Updated and Watch Conversation Created, are instant: Gmelius calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. That is why you click Create a webhook before Create a connection when you add one. The scenario still has to be switched on, and on the Free plan it counts toward your 2 active scenarios. Nothing else needs tuning.
04What if the Gmelius module you need is missing in Make?
Use Make an API Call. It is part of the Gmelius app in Make and sends a request to any endpoint of the Gmelius API with the connection you already set up. That covers what the 12 action and search modules leave out. You will need the Gmelius API documentation to write the request. The Make documentation page for Gmelius also warns that its content is AI generated and may contain mistakes, so check anything critical with Gmelius.
05Make or n8n for Gmelius?
It depends on what your scenario needs. In Make, Gmelius comes with 14 ready modules, 2 instant triggers and Make an API Call, which covers the usual inbox and board work without code. Before choosing n8n, check whether it offers a Gmelius node and whether that node has the actions you plan to use. The deciding criteria are the modules available for your case and the tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations