Connect Mautic Webhooks to Your Sales Pipeline

Connect inbound deal data and outbound events

A Mautic webhook integration can connect external tools and a sales pipeline in two directions. Inbound requests send deal data into Mautic through a signed endpoint. Outbound event subscriptions notify external automation when a deal is created, changes stage, is won, or is lost. Use HMAC-SHA256 verification for incoming requests, then subscribe to the deal events each downstream workflow needs.

Deal Flow provides the pipeline layer for this pattern. Its inbound webhook sources accept mapped deal data and documented contact data, while its deal events use Mautic’s native outbound webhook system. The result is a focused event path into and out of the pipeline, without turning this guide into an endpoint or payload reference.

Capabilities verified August 24, 2026 against the Deal Flow webhook reference. Source routing, HMAC secrets, deal-field mapping, and published state were also checked against the product specification.

Choose the direction your workflow needs

Use both directions when intake begins elsewhere and later pipeline changes need to continue the workflow. They are separate event paths: an inbound source accepts a signed request, while an outbound subscription sends selected events to a destination you control.

Source: Webhook overview, checked August 24, 2026.

Set up a signed inbound deal path

1. Create and publish a source. Give the source a clear name and choose the default pipeline for new deals created through it.
2. Map the incoming data. Align the sender’s deal values through the source mapping, and use the documented contact object for identity. The reference covers title, amount, close date, contact identity, and custom-field input without requiring you to copy a fixed example from this guide.
3. Sign the exact request body. Compute an HMAC-SHA256 digest from the raw bytes you will send, using that source’s secret, and place the result in X-DealFlow-Signature.
4. Test the resulting record. Send a representative request, then confirm the intended pipeline, deal values, and contact association before enabling the production sender.

Missing or invalid signatures receive HTTP 403. Keep the exact endpoint shape, signature procedure, supported field names, and request examples in one place by following the HMAC signing reference and inbound payload reference.

Inbound source, signing, and field details checked August 24, 2026 against the linked webhook reference.

Route pipeline events into external automation

In Mautic → Settings → Webhooks, configure the destination and select the deal events that matter to the downstream workflow. For this workflow, focus on four lifecycle events:

• dealflow.deal.created — use when a downstream process should begin after a deal is created.
• dealflow.deal.stage_changed — use when a stage move should start a notification, handoff, or external automation.
• dealflow.deal.won — use when a downstream system should begin a won-deal process.
• dealflow.deal.lost — use when a downstream system should close or reroute its workflow.

These are event signals, not native connectors to the destination tools. Your receiving endpoint or automation layer decides what each signal does. See the outbound event reference for the complete documented catalog and the example event structure.

Event names and Mautic settings path checked August 24, 2026 against the linked webhook reference.

Follow one workflow from intake to outcome

1. An external system prepares deal data. A form, application, or automation layer maps its values to the documented inbound fields.
2. The sender signs and posts the request. It uses the inbound source’s secret and source-specific endpoint.
3. A new deal enters the selected pipeline. Deal Flow applies the deal-field mapping, uses the source’s default pipeline for the new deal, and associates the contact by the documented email path.
4. The team advances the deal. Normal pipeline work changes its stage or outcome inside Mautic.
5. Mautic sends the selected event. The external endpoint receives the lifecycle signal and continues its own workflow.

Use the right implementation reference

• Use the webhook reference for exact endpoints, signing rules, inbound fields, event names, and payload examples.
• Use the Mautic and n8n guide when you want a visual workflow-builder route for deal automation.
• Use the deal-stage campaign guide when a mapped stage should feed a contact-based Mautic campaign instead of an external endpoint.

This page helps you choose and sequence the integration. The reference remains the source for field-level implementation details.

Check the path before you activate it

• Use a separate inbound source and secret for each sending integration.
• Confirm the source’s default pipeline for new deals and its deal-field mapping with representative data.
• Sign the exact raw body and verify the signature header on a test request.
• Subscribe only to the outbound events the receiving workflow uses.
• Test creation, stage movement, won, and lost paths independently.
• Keep the public webhook reference beside your implementation for exact contract details.

Frequently asked questions

Can Mautic webhooks create or update deals?

Yes. With a configured Deal Flow inbound source, an external system can POST documented deal data to that source’s endpoint. Field mapping handles deal values, while the source’s default pipeline applies to newly created deals.

How are inbound webhook requests verified?

The sender computes an HMAC-SHA256 digest over the exact raw request body using that source’s secret and sends it in X-DealFlow-Signature. Requests with missing or invalid signatures receive HTTP 403.

Which deal changes can trigger outbound automation?

The documented lifecycle events include dealflow.deal.created, dealflow.deal.stage_changed, dealflow.deal.won, and dealflow.deal.lost. The webhook reference lists the full event catalog.

Where are the exact webhook fields and examples?

Use the webhook reference for endpoint, signing, payload, and event details. Use the n8n guide for a visual workflow-builder route, or the deal-stage campaign guide when the next action belongs in a Mautic campaign.