Skip to content
Per-pair page

Connect Mautic to Gmail in two minutes.

Real-time triggers from Mautic, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.

Trigger app
Mautic as the trigger

Workflows fire when something happens in Mautic.

Action app
Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

MauticGmail

When something happens in Mautic, do it in Gmail.

5 Mautic triggers wired to 27 Gmail actions. Most-used pairing: Mautic Contact CreatedAdd Labels to Message.

GmailMautic

Or fire it the other way around.

1 Gmail triggers wired to 2 Mautic actions downstream.

See GmailMautic
Popular pairings

Common Mautic → Gmail workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations
When mautic contact created in Mautic, add labels to message in Gmail.

Fires when a new contact lands in Mautic. The base hook for "new lead in Mautic → push to CRM and downstream tools" workflows.

When mautic contact created in Mautic, create draft in Gmail.

Fires when a new contact lands in Mautic. The base hook for "new lead in Mautic → push to CRM and downstream tools" workflows.

When mautic contact created in Mautic, create label in Gmail.

Fires when a new contact lands in Mautic. The base hook for "new lead in Mautic → push to CRM and downstream tools" workflows.

When mautic contact created in Mautic, delete draft in Gmail.

Fires when a new contact lands in Mautic. The base hook for "new lead in Mautic → push to CRM and downstream tools" workflows.

When mautic contact updated in Mautic, add labels to message in Gmail.

Fires on any contact field change including segment memberships. For granular state-change reactions, inspect the changed fields in the payload.

When mautic contact updated in Mautic, create draft in Gmail.

Fires on any contact field change including segment memberships. For granular state-change reactions, inspect the changed fields in the payload.

When mautic contact updated in Mautic, create label in Gmail.

Fires on any contact field change including segment memberships. For granular state-change reactions, inspect the changed fields in the payload.

When mautic contact updated in Mautic, delete draft in Gmail.

Fires on any contact field change including segment memberships. For granular state-change reactions, inspect the changed fields in the payload.

When mautic email opened in Mautic, add labels to message in Gmail.

Fires once per recipient per email on first open. For engagement-based scoring or warm-lead detection workflows.

How it works

Connect Mautic and Gmail in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Mautic and Gmail

    Open Tiny Command, authorize Mautic and Gmail once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Mautic trigger

    Drop the Mautic → Mautic Contact Created trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/mautic.trigger-contact-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Gmail action

    Drop the Gmail → Add Labels to Message action below it. Map fields from the Mautic payload into the Gmail inputs.

    google-gmail.add-labels
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Mautic + Gmail.

How long does it take to connect Mautic and Gmail on Tiny Command?
Under two minutes. Authorize Mautic and Gmail once each, drop the Mautic trigger and Gmail action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Mautic ↔ Gmail integration real-time?
Yes. Both Mautic and Gmail expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Mautic and Gmail?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Gmail.
What Mautic events can trigger a Gmail workflow?
Any of the 5 Mautic triggers, including "Mautic Contact Created". Each fires in real time when the matching event happens in Mautic.
Do I need a paid plan to use Mautic with Gmail?
No. There's a free tier that covers most Mautic+Gmail use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Gmail → Mautic instead?
Build it the same way, in reverse. There's a dedicated /integrations/google-gmail/with/mautic page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Mautic.


Wire Mautic to Gmail in 2 minutes.

Free tier available. No credit card. No onboarding call.