🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Keep Shopify and Mautic consent in sync

Keep Shopify and Mautic consent in sync - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Keep Shopify and Mautic consent in sync - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your email list looks fine until it doesn’t. A customer opts out in Shopify, stays opted in inside Mautic, and suddenly you’re sending campaigns to people who very clearly told you “no.”

This is the kind of mess that hits ecommerce managers first, but marketers running Mautic and ops folks handling data hygiene feel it too. With Shopify Mautic consent automation, subscription changes stay aligned both ways, so segments stay clean and complaints drop.

This workflow keeps consent updates moving automatically, explains the logic in plain English, and shows what you need to get it running safely.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Keep Shopify and Mautic consent in sync

The Problem: Consent Drifts Between Shopify and Mautic

Consent isn’t static. Customers opt in at checkout, unsubscribe from a campaign, re-subscribe after a product drop, or change their mind again two weeks later. When Shopify and Mautic don’t talk, those changes split into two “truths,” and your team ends up guessing which one to trust. The fallout is real: you lose confidence in segments, you waste time fixing records, and you take on compliance risk because the same person can be treated as subscribed in one system and unsubscribed in the other.

It adds up fast. Here’s where it usually breaks down.

  • Someone unsubscribes via an email footer, but Shopify still shows them as opted in, so a future sync or import can quietly re-subscribe them.
  • Lists get “cleaned” manually before a campaign, which means last-minute spreadsheet work and missed sends when you’re already under deadline.
  • Customer service gets dragged into it after complaints, because nobody can quickly explain where the opt-in status came from.
  • Segmentation rules inside Mautic become unreliable, so personalization gets weaker and reporting starts to lie.

The Solution: Two-Way Consent Sync With n8n

This n8n workflow is built as a two-way bridge between Shopify and Mautic. On the Shopify side, it watches for customer marketing preference changes and then looks up the matching contact in Mautic by email. If the contact exists, the workflow updates their status by adding or removing them from a “confirmed” group (and it can create the contact if you choose). On the Mautic side, it listens for webhook events, verifies the request signature for safety, fetches the correct Shopify customer record via the Admin API (GraphQL), and then updates Shopify’s email marketing consent to match what happened in Mautic. No plugins, no brittle exports, no weekly “sync day.”

The workflow starts with either a Shopify update trigger or an incoming Mautic webhook. It checks consent rules using simple IF logic, then updates the other system using the Mautic API and Shopify GraphQL calls. When something doesn’t match (invalid signature, missing customer, missing contact), it stops cleanly instead of forcing bad updates.

What You Get: Automation vs. Results

Example: What This Looks Like

Let’s say you run two campaigns a week and you do a consent cleanup before each send. Manually, that often means exporting from Shopify, checking statuses in Mautic, chasing duplicates, then updating records, which can easily take about 2 hours per cleanup (so roughly 4 hours a week). With this workflow, the “cleanup” becomes checking a small log when you want peace of mind. Consent updates happen as they occur, and you spend a few minutes reviewing instead of burning an afternoon fixing drift.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Shopify as the consent source and customer database
  • Mautic to store marketing consent and segments
  • Shopify Admin API access token (create a custom app in Shopify)

Skill level: Intermediate. You’ll connect APIs, paste credentials, and test a webhook signature check.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A Shopify customer update kicks off the first sync. When a customer’s email marketing preference changes in Shopify, n8n catches it via the Shopify trigger and immediately looks up the matching email in Mautic.

The workflow checks if the contact exists and what the opt-in status should be. If the contact is found, IF rules decide whether to append them to a confirmed group or remove them. If the contact isn’t found, the workflow can generate a new contact first, then apply the right group status.

A Mautic webhook handles the “other direction.” Mautic events arrive through an incoming webhook, and the workflow calculates an HMAC signature hash and compares it before doing anything else. If the signature doesn’t match, it stops. Good.

Shopify gets updated through GraphQL and only when the customer exists. After verification, the workflow queries Shopify (GraphQL) to find the customer record, checks for a match, then sets consent to subscribed or unsubscribed based on the Mautic opt-in state. Missing customer records route to a “no-op” branch so you don’t accidentally create junk updates.

You can easily modify group names and consent rules to match your process based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Shopify Trigger

Set the Shopify trigger to fire on customer profile updates and connect your Shopify credentials.

  1. Add Shopify Update Trigger and set Topic to customers/update.
  2. Set Authentication to accessToken.
  3. Credential Required: Connect your shopifyAccessTokenApi credentials.

Step 2: Connect Mautic for Contact Lookup and Segments

Configure Mautic to look up contacts, create new contacts, and manage segment membership based on Shopify consent.

  1. In Lookup Contact Email, set Operation to getAll, Limit to 1, and Search to {{ $json.email }}.
  2. Credential Required: Connect your mauticOAuth2Api credentials to Lookup Contact Email, Append to Confirmed Group, Remove from Confirmed Group, and Generate New Contact.
  3. In Append to Confirmed Group, set Resource to contactSegment, Segment ID to 1, and Contact ID to {{ $json.id }}.
  4. In Remove from Confirmed Group, set Operation to remove, Segment ID to 1, and Contact ID to {{ $json.id }}.
  5. In Generate New Contact, map Email to {{ $('Shopify Update Trigger').item.json.email }}, First Name to {{ $('Shopify Update Trigger').item.json.first_name }}, and Last Name to {{ $('Shopify Update Trigger').item.json.last_name }}.

Step 3: Set Up Webhook Verification and Shopify Subdomain

The webhook path listens for Mautic subscription events, verifies the signature, and defines the Shopify subdomain. Incoming Webhook Listener outputs to both HMAC Signature Hash and Define Shopify Subdomain in parallel.

  1. In Incoming Webhook Listener, set HTTP Method to POST and Path to 6485fca6-c641-4067-b19a-192709b88e45.
  2. Enable Raw Body in Incoming Webhook Listener options to compute the HMAC signature.
  3. In HMAC Signature Hash, set Type to SHA256, Action to hmac, Encoding to base64, and Binary Data to true.
  4. In Define Shopify Subdomain, set Shopify Subdomain to [YOUR_SHOPIFY_SUBDOMAIN].

⚠️ Common Pitfall: Replace [CONFIGURE_YOUR_TOKEN] in HMAC Signature Hash with your Shopify webhook signing secret, or the Signature Match Check will fail and route to No-Op Invalid Signature.

Step 4: Configure Consent Routing with IF Nodes

Use conditional logic to route existing and new contacts and keep Mautic segments synced with Shopify marketing consent.

  1. In Verify Contact Presence, keep the condition checking Left Value {{ $json.id }} with operator exists.
  2. In both Check Marketing Opt-In and Check Marketing Opt-In B, set the condition to {{ $('Shopify Update Trigger').item.json.email_marketing_consent.state }} equals subscribed.
  3. Ensure the true path of Check Marketing Opt-In goes to Append to Confirmed Group, and the false path goes to Remove from Confirmed Group.
  4. Ensure the true path of Check Marketing Opt-In B goes to Generate New Contact, and the false path goes to Do Nothing Placeholder.

Step 5: Sync Mautic Subscription Changes Back to Shopify

When Mautic notifies a subscription change, validate the webhook, query the customer, and update Shopify consent via GraphQL.

  1. In Signature Match Check, keep the comparison between {{ $('Incoming Webhook Listener').item.json.headers['webhook-signature'] }} and {{ $json.data }}.
  2. In Shopify GraphQL Query, set Endpoint to https://{{ $('Define Shopify Subdomain').params["fields"]["values"][0]["stringValue"] }}.myshopify.com/admin/api/2024-01/graphql.json and keep the provided Query expression.
  3. Credential Required: Connect your httpHeaderAuth credentials to Shopify GraphQL Query, Set Consent Subscribed, and Set Consent Unsubscribed.
  4. In Mautic Opt-In Check, set the condition to {{ $('Incoming Webhook Listener').item.json.body['mautic.lead_channel_subscription_changed'][0].new_status }} equals contactable.
  5. In Set Consent Subscribed and Set Consent Unsubscribed, keep the Variables JSON with {{ $json["data"]["customers"]["edges"][0]["node"]["id"] }} and {{ $now }} values.

Tip: If Confirm Customer Exists evaluates false, the workflow routes to No-Op Customer Missing, which is a safe stop to avoid updating non-existent Shopify records.

Step 6: Test and Activate Your Workflow

Verify both Shopify-triggered updates and Mautic webhook updates before turning on the workflow in production.

  1. Click Test workflow and trigger a customer update in Shopify; confirm data reaches Lookup Contact Email and flows through Verify Contact Presence.
  2. Send a test request to the Incoming Webhook Listener URL and confirm the flow passes Signature Match Check and reaches Shopify GraphQL Query.
  3. Successful execution should either add/remove the contact in Mautic via Append to Confirmed Group/Remove from Confirmed Group or update Shopify via Set Consent Subscribed/Set Consent Unsubscribed.
  4. Toggle the workflow Active to enable continuous syncing.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Shopify credentials can expire or lack the right scopes for Admin API access. If updates stop, check your custom app permissions and the access token you stored in n8n first.
  • If you’re relying on webhook verification, one wrong secret breaks everything. Confirm the webhook secret in Mautic matches what your HMAC node uses, then re-send a test event to validate.
  • Mautic contact matching by email sounds simple, but aliases and typos create “missing contact” cases. Decide upfront if you want the workflow to create new contacts automatically or route them to review.

Related Workflows

If you’re also trying to keep acquisition lists fresh, Shopify to Mautic, new customers captured instantly pairs nicely with consent sync, because it ensures new buyers enter Mautic quickly without manual imports.

For teams running multiple storefronts, WooCommerce to Mautic, contacts always campaign ready helps standardize how contacts arrive in Mautic, so consent policies and segmentation rules stay consistent across platforms.

Need a safety net before big sends? Mautic + Slack: catch bad emails before campaigns is useful when list quality is the hidden reason campaigns underperform (and it saves support time too).

When duplicates are your real enemy, Shopify meets Odoo for duplicate free customer contacts adds a clean-up layer that keeps contact records consistent across systems, which indirectly makes consent management less chaotic.

Finally, if you want customer conversations tied to clean profiles, Shopify to Zendesk, contacts stay clean and current keeps support records accurate, so agents don’t message people who opted out or have outdated details.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Shopify Mautic consent automation?

Plan on about 45 minutes if you already have Shopify and Mautic API access.

Do I need coding skills to automate Shopify Mautic consent sync?

No. You’ll mostly copy credentials, set a few values, and run test events.

Is n8n free to use for this Shopify Mautic consent workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Shopify and Mautic running costs (the workflow itself does not require paid AI APIs).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Shopify Mautic consent automation for double opt-in only?

Yes, but be strict about the rule. You can change the logic in the “Check Marketing Opt-In” and “Mautic Opt-In Check” decision nodes so only confirmed (double opt-in) contacts get added to your confirmed group or marked as subscribed in Shopify. Common customizations include mapping different Mautic segments, using a different group name, and routing uncertain cases to a review queue instead of auto-updating.

Why is my Shopify connection failing in this workflow?

Usually it’s an access token issue. Regenerate the Shopify custom app token, confirm it has the right Admin API scopes, and update both the Shopify Trigger credentials and the header auth used by the GraphQL requests. If it fails only during spikes, you may be hitting rate limits, so spacing events or adding retry logic can help. Also confirm the workflow is using the right Shopify subdomain value in the “Define Shopify Subdomain” step.

How many consent updates can this Shopify Mautic consent automation handle?

A lot. On n8n Cloud, capacity depends on your plan’s monthly executions, and self-hosting depends on your server. Practically, consent events are lightweight, so most small shops can run this all day without noticing.

Is this Shopify Mautic consent automation better than using Zapier or Make?

Often, yes. The big reason is bidirectional sync with guardrails: webhook signature validation, branching logic, and GraphQL calls are all normal in n8n, while other tools can get expensive or awkward once you go beyond a simple two-step zap. n8n also gives you the option to self-host, which is handy if you process lots of small events. If you only need a one-way update and you never want to touch a webhook secret, Zapier or Make can still be simpler. If you’re unsure, Talk to an automation expert and you’ll know quickly.

Once consent stays synced, your segments stop drifting and your team stops second-guessing every send. Set it up, test it, and let the workflow do the boring part.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.