How to Trigger Mautic Campaigns from Deal Stage Changes

The short answer

Map each deal stage to a Mautic contact stage, then use a public, stage-filtered contact segment as the source for a Mautic campaign. When the deal moves, update the associated contacts to the mapped contact stage. After Mautic’s segment and campaign jobs run, matching contacts enter the campaign. If the response belongs outside Mautic, send the deal stage-change event to an endpoint with an outbound webhook.

Deal Flow supplies the bridge: an optional mapping connects a pipeline stage to a Mautic contact stage, and a mapped deal move updates the contacts associated with that deal. Mautic’s existing segment and Campaign Builder logic handles what happens next.

Mautic behavior checked August 22, 2026 against the official Stages documentation, Segments documentation, Campaign Builder documentation, and cron-job documentation.

How a deal stage reaches a Mautic campaign

1. The deal moves. A deal enters a pipeline stage that has a Mautic contact-stage mapping.
2. Associated contacts sync. Deal Flow changes every contact associated with that deal to the mapped Mautic stage.
3. Mautic rebuilds the segment. A dynamic segment filtered to that contact stage gains the contacts after the segment job runs.
4. The campaign processes those contacts. Use that public segment as the campaign source, then let Mautic’s campaign jobs enroll and process its members.

Configure the stage-sync side first

1. Create active Mautic contact stages

Create the contact stages that should represent the campaign moments you need, such as Qualified or Proposal. Keep them active so they appear in segment filters and Campaign conditions. Mautic also uses stage weight as forward progression and does not move a contact to a lower-weight stage, so order the mapped stages deliberately. The official stage guide documents both behaviors.

2. Map the corresponding Deal Flow stages

For each pipeline stage that should become an automation signal, select the matching Mautic contact stage in Deal Flow’s stage mapping. A mapping is optional. An unmapped deal stage remains a valid pipeline stage, but moving a deal there does not supply this contact-stage signal.

3. Check the deal’s contact associations

Stage sync updates every contact associated with the deal. That is useful when several members of a buying committee should enter the same workflow, but it can also enroll more than one person from the account. Associate only the contacts whose lifecycle stage should follow that deal.

Build the campaign with Mautic’s native pieces

1. Create a dynamic segment for the target contact stage

In Mautic, create an active, public segment and add a Stage filter for the mapped contact stage. Dynamic segment membership follows changes to contact data, and Mautic rebuilds those memberships on the configured segment-job cadence. Mautic’s segment documentation explains the filter and rebuild model.

2. Use that segment as the campaign source

Create a Campaign and select the stage-filtered segment as its contact source. Add the native actions you need after enrollment: send an email, notify a user, change tags, update contact data, or call a webhook. The Campaign Builder documentation lists the supported sources, conditions, decisions, and actions.

3. Confirm Mautic’s scheduled jobs

This path runs on Mautic’s normal background processing. The segment job must rebuild membership, the campaign job must update membership, and the campaign trigger job must process scheduled events. The delay between a deal move and a Campaign action therefore follows your job schedule; Mautic’s cron-job documentation lists all three required jobs.

Worked example: Proposal follow-up

Suppose a pipeline has a deal stage named Proposal, and Mautic has an active contact stage with the same business meaning.

1. Map the Deal Flow Proposal stage to the Mautic Proposal contact stage.
2. Associate the intended Champion and Decision Maker contacts with the deal.
3. Create a public Mautic segment filtered to contacts in the Proposal stage.
4. Use that segment as the source for a Proposal follow-up Campaign.
5. Move a test deal to Proposal and verify both contact-stage changes before testing Campaign enrollment.

When the mapped deal move occurs, both associated contacts receive the contact-stage update. After the scheduled jobs run, both can enter the Campaign. If only one person should receive the workflow, narrow the contact associations or add a contact-level filter before activation.

Use an outbound webhook for external automation

If the next step belongs outside Mautic, subscribe to dealflow.deal.stage_changed in Mautic → Settings → Webhooks and send the event to your integration endpoint. This path carries the deal change outward without presenting it as a Mautic Campaign trigger.

Mautic’s webhook system handles delivery, queuing, retries, and logs. The Deal Flow webhook guide documents the available event and example stage-change payload.

• Use stage sync when the next step is a contact-based Mautic Campaign.
• Use the outbound event when an external automation service, notification endpoint, or data system needs the deal change.
• Use both when Mautic should run a contact workflow and an external system should receive the same business event.

Know the limits before activation

• No native deal Campaign conditions or actions: Deal Flow does not currently add Campaign conditions for deal fields or stages, and it does not add actions that move or update deals.
• Mappings and associations are required: an unmapped deal stage or a deal with no associated contacts cannot produce the contact-stage signal described here.
• Campaign execution remains contact-based: each associated contact is evaluated and processed separately, even when they belong to the same deal.
• Mautic stage rules still apply: stage weight limits backward contact movement, and scheduled jobs determine when segment and Campaign processing occurs.

The practical pattern is narrow and dependable: use Deal Flow to synchronize deal state into an existing Mautic contact-stage signal, then build with the Mautic campaign tools that already understand contacts.

Frequently asked questions

Can a Deal Flow deal stage trigger a Mautic campaign?

Not directly. Map the Deal Flow stage to a Mautic contact stage and associate contacts with the deal. When the deal moves, stage sync updates those contacts; Mautic can then enroll matching contacts through a stage-filtered segment used as the campaign source.

Which contacts are updated when a mapped deal stage changes?

Deal Flow updates every contact associated with the deal. Because campaign enrollment is contact-based, review buying-committee associations before using a mapped stage as an automation signal.

Does Deal Flow add campaign conditions or actions for deals?

No. Deal Flow does not currently provide native Mautic campaign conditions or actions for deal fields, deal stages, or deal moves. This guide uses Deal Flow’s contact-stage sync as a bridge into Mautic’s existing segment and campaign system.

When should I use the outbound webhook instead?

Use the outbound webhook when the next action belongs in an external service or automation tool. Subscribe to dealflow.deal.stage_changed in Mautic’s webhook settings and send the event to your endpoint.