Resources · Zapier integration

Gmelius Zapier integrationAutomate Gmelius with Zapier.

The Gmelius Zapier integration gives you 8 triggers and 6 actions, all built around shared inboxes, Kanban boards in Gmail and email sequences. Every trigger is instant, the app works on the free plan, and three actions need an item made earlier in the same Zap.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Gmelius Zapier integration actually does

Gmelius is a team email tool that lives inside Gmail: shared inboxes, Kanban boards and email sequences. Zapier connects it to your other apps through a Zap, an automation made of one trigger (the event that starts it) and one or more actions (what it does next). With Gmelius, every trigger is instant, so nothing waits for a scheduled check.

Three results teams usually build first. A support board that fills itself: New Conversation on a shared inbox, then Create Card on the right board and column. A sales handoff: New Sequence Unenrollment tells you a contact left a sequence, so someone can pick the thread up. A clean task trail: Updated Card sends status or assignee changes to wherever your team reports. Each of those three results starts on an instant trigger, so the card or the alert shows up as soon as Gmelius reports the event.

Now what Zapier does not do here. There is no search step, so a Zap cannot look up an existing card or conversation by name. Update Card, Update Conversation and Create Conversation Draft only work on an item created in an earlier step of the same Zap. And no action deletes anything.

If you are still weighing tools, the Gmelius Make integration covers the same app on Make, and the Zapier review is there if you are weighing Zapier itself.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for it to happen.
Action
What the Zap does after it starts: the step that creates a card, enrolls a contact or writes a draft for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts these and nothing else.
Instant vs polling trigger
An instant trigger is reported by the app itself, right away. A polling trigger is checked by Zapier on a timer. Gmelius only has instant ones.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What a Gmelius Zap really costs

The trigger is free. Zapier only bills the actions that go through.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Gmelius on freeYes, it is not a premium app
  • Trigger speedInstant on all 8, whatever the plan

Each successful action counts as one task, so a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted, and listening for new events costs nothing. Gmelius is not a premium app, so it runs on the free plan, but that plan stops at two steps: a filter or a second action means a paid plan. Since every Gmelius trigger is instant, your plan changes how many steps and tasks you get, never how fast a Zap starts.

Connect

Connect Gmelius to Zapier in 3 steps

  1. 01

    Open your apps

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your Gmelius account linked to Zapier once, then reused by every Zap that needs it.

  2. 02

    Pick Gmelius

    Type Gmelius in the search box of the dialog, select it, then click Add connection. Zapier opens a new tab where Gmelius asks you to sign in to your account.

  3. 03

    Sign in and allow access

    Log in with the Gmelius account your team works in and grant Zapier access. You need read or write rights on every shared inbox, board or sequence you did not create yourself but want a Zap to touch.

First Zap

Your first Zap: every new conversation becomes a tracked card

GoalA support lead wants each new email in the shared help inbox to land as a card, already assigned, on the team board.

  1. 01

    Build: set the trigger

    Create a Zap, pick Gmelius and the New Conversation event, then choose the shared inbox or shared label to watch. That choice is required.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent conversations from that inbox, so you map the next steps on a real email, not on a blank form.

  3. 03

    Add Create Card

    Add the Create Card action. Pick the board and the column, then build the card title from what the conversation brought back.

  4. 04

    Add Update Card

    Add Update Card and point it at the card made one step earlier. Use it to assign the card, set a status or a due date. This second action makes the Zap multi-step.

  5. 05

    Test, then Publish

    Test each action once and check the card in Gmail. When it looks right, click Publish to switch the Zap on. Each run then costs two tasks.

Triggers

Gmelius triggers: the 8 events that start a Zap

8 events start a Zap when something happens in Gmelius, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Updated Card

Instant trigger

In Zapier“Triggers when a card is updated within a Kanban board in Gmail.”

Fires when someone changes a card on one of your Kanban boards in Gmail, so a status move or a new assignee can reach the rest of your tools without anyone retyping it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a project lead wants a log line each time a client card moves to the done column.
Watch out
both the board and the kind of update to follow are required settings.
2

Updated Conversation

Instant trigger

In Zapier“Triggers when email assignee, status, or tag is added or changed.”

Starts the Zap when a shared email changes hands or state: a new assignee, a different status, or a tag added or changed on the conversation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an account manager wants to know as soon as a key customer thread gets tagged for escalation.
Watch out
the step needs a shared inbox or shared label and an update type, so a personal thread outside them is never seen.
3

New Card

Instant trigger

In Zapier“Triggers when a new card is created within a Kanban board in Gmail.”

Reacts to every card added on a chosen Kanban board in Gmail.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency owner wants each new client request card copied into the tool where the team plans its week.
Watch out
if a Zap on this trigger also runs Create Card on the same board, it feeds itself and burns tasks in a loop.
4

New Conversation

Instant trigger

In Zapier“Triggers when a new conversation is received within a Gmelius workspace.”

Catches each new conversation received in your Gmelius workspace, which makes it the natural starting point for anything that should happen when a customer writes in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a helpdesk lead turns every email in the support inbox into a card the team can sort.
Watch out
you have to choose one shared inbox or shared label; a Zap only listens to that one.
5

New Reply to Conversation

Instant trigger

In Zapier“Triggers when a new email appears in a thread within a Gmelius workspace.”

Goes off when a fresh email lands in an existing thread, not only when the thread starts, so follow-ups and customer replies are not missed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales rep wants a ping the second a prospect answers in the shared deals inbox.
Watch out
every reply counts, including your team's own answers, so plan a filter if only customer emails matter.
6

New Note

Instant trigger

In Zapier“Triggers when a new note is added to an email or a task card.”

Watches the internal notes your team adds on an email or on a task card.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an operations manager collects every note left on refund threads into one shared review list.
Watch out
the note type is required, so decide up front whether the Zap follows notes on emails or notes on cards.
7

New Sequence Enrollment

Instant trigger

In Zapier“Triggers when a contact is added to a sequence in Gmelius.”

Tells Zapier each time a contact joins one of your Gmelius sequences.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a growth marketer keeps a running record of who entered the onboarding sequence, and pairs it with Create Card to give each newcomer a card on the sales board.
Watch out
the sequence to follow is a required setting, so pick it before you run the test.
8

New Sequence Unenrollment

Instant trigger

In Zapier“Triggers when a contact is removed from a sequence in Gmelius.”

The mirror of the previous one: it fires when a contact is taken out of a sequence, which is often the moment a human should step in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a founder doing outbound wants a follow-up card whenever a prospect leaves the cold sequence.
Watch out
the Zap only listens to the sequence you set, and that setting is required.
Actions

Gmelius actions: what a Zap can do for you

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

1

Create Card

Action

In Zapier“Creates a new task card within a Kanban board in Gmail.”

Adds a new task card on a Kanban board in Gmail, in the column you choose, with the title you build from earlier steps.

When to use it
turn a form entry, a new deal or an incoming email into something your team can drag across the board.
Watch out
the board, the column and the title are all required, and the board must already exist.
2

Enroll in Sequence

Action

In Zapier“Adds a contact in a sequence in Gmelius.”

Puts a contact into one of your Gmelius sequences from an email address, so the follow-ups start without anyone opening Gmail.

When to use it
a webinar sign-up or a trial account should start a nurture sequence straight away.
Watch out
both the sequence and the email address are required for each run.
3

Create Conversation Draft

Action

In Zapier“Adds a draft to a conversation.”

Writes a draft inside a conversation without sending it, so a person reviews the wording before it goes out.

When to use it
prepare a standard answer on a thread that just came in through New Conversation, then let the team polish and send it.
Watch out
the conversation must come from an earlier step of the same Zap, picked through its ID in the Custom tab.
4

Unenroll From Sequence

Action

In Zapier“Removes a contact from a specific sequence in Gmelius.”

Takes a contact out of a specific sequence, the clean way to stop automated follow-ups once a person has answered or bought.

When to use it
a deal marked as won elsewhere should stop the prospecting emails at once.
Watch out
it only removes from the sequence you name.
5

Update Card

Action

In Zapier“Updates a task card : add tag, change status, assign, change due date.”

Changes a card already on a board: add a tag, change its status, assign it or move its due date.

When to use it
right after Create Card, assign the new card to the person on duty.
Watch out
the card has to be created in an earlier step of this Zap and picked by its ID in the Custom tab.
6

Update Conversation

Action

In Zapier“Updates a conversation : add tag, add note, change status, assign.”

Edits a shared conversation: add a tag or a note, change the status, or hand it to a teammate.

When to use it
tag and assign a thread the moment it comes in through New Conversation, so nobody has to triage it by hand.
Watch out
like the draft action, it needs a conversation from an earlier step of the same Zap, chosen through its ID.
When it breaks

When a Gmelius Zap breaks

Zapier lists no Gmelius-specific help article, so the traps below are the general ones, applied to this app.

Trouble comes from what a Zap does not see, or from a Zap that sees too much. If a run fails, start with the Zapier troubleshooting page.

  • Old conversations are ignored

    A Zap only reacts to what happens after you publish it. Threads and cards that already existed are never picked up; moving that backlog is a separate job.

  • The card loop

    New Card watching a board while Create Card writes on that same board makes the Zap set itself off again and again, and your task count drains fast.

  • A bulk import stalls

    If a trigger suddenly sends a huge batch, after a migration for instance, Zapier's flood protection can hold the runs back.

  • Update steps with nothing to update

    Update Card, Update Conversation and Create Conversation Draft need an item from an earlier step of the same Zap. Without it, the step has no target.
Need help

Need help automating Gmelius with Zapier?

A person reads every message.

FAQ

Gmelius Zapier integration: common questions

01Is the Gmelius Zapier integration free?
Yes, you can use it on the free Zapier plan, because Gmelius is not a premium app. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter or a second action, such as Update Card after Create Card, the Zap becomes multi-step and needs a paid plan. Start with a two-step Zap to check the result before you pay.
02How many tasks does a Gmelius Zap use?
One task per action that completes successfully, and nothing for the trigger. A Zap that creates a card uses one task per new conversation. Add Update Card behind it and every run uses two. An action that fails is not billed, and Zapier listening for new Gmelius events costs nothing at all. Watch the loop case: a Zap that creates cards on the board its own trigger watches can spend a whole month of tasks very fast.
03Do Gmelius triggers run in real time?
Yes. All 8 Gmelius triggers are instant: Gmelius tells Zapier the moment a card, a conversation, a note or a sequence change happens. The plan intervals that slow down polling triggers, 15 minutes on the free plan, do not apply here. Paid plans bring that interval down to one minute, yet it never concerns Gmelius, whose triggers wait for no check. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect Gmelius to Zapier?
A Gmelius account, and read or write access to every shared inbox, board or sequence you did not create yourself but want a Zap to use. The connection is added once from the Apps page with + Add connection, then reused by all your Zaps. Before building, make sure the boards, columns, shared inboxes and sequences you need already exist in Gmelius, since most steps ask you to pick one. The tab that opens is where you sign in.
05Why can't a Zap update an existing Gmelius card?
Because Update Card only accepts a card created in an earlier step of the same Zap, selected through its Card ID in the Custom tab. The same rule applies to Update Conversation and Create Conversation Draft. There is no Gmelius search step on Zapier, so a Zap cannot look up an older card or thread by name. Build the Zap so that it creates the item first, then updates it.
06What if the Gmelius action you need is not on Zapier?
Then the integration simply does not offer it today: Zapier shows 8 triggers and 6 actions for Gmelius, with no search and no delete action. The six actions create, update, enroll or unenroll; none removes a card or a conversation. You can still chain what exists, for instance create a card then update it. Anything outside that list cannot be built with this integration as it stands, so check the list of operations before you commit to a Zap design.
07Zapier, Make or n8n for Gmelius?
It depends on your criteria, not on a winner. Look at three things: which Gmelius operations each tool offers, how it bills the volume you expect, and how many steps your workflow really needs. On Zapier, all 8 Gmelius triggers are instant even on the free plan, but any Zap beyond two steps needs a paid plan. Run the same check on the other two tools before you decide, using the operations list of each.
Same platform

Other docs you might need on this stack.

Browse all integrations