Mautic trigger

Overview

Receives webhook notifications from a Mautic instance when configured marketing automation events fire. Mautic is an open-source marketing automation platform. The trigger registers a webhook with the Mautic API that listens for specified events such as contact creation, form submissions, email opens, page hits, and point changes. The raw POST body from Mautic is returned as the output payload. Events can be ordered ascending or descending when multiple events are queued in a single webhook delivery. Supports both Basic Auth (username/password) and OAuth2 authentication against self-hosted Mautic instances. Useful for triggering workflows when contacts are created or updated, forms are submitted, emails are interacted with, or campaign events fire in Mautic.

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Mautic credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Authentication	options	No	credentials	Authentication method to use for Mautic API calls.
				Options: credentials, oAuth2
Events	multiOptions	Yes	[]	Which Mautic events to listen for, chosen from the well-known Mautic webhook trigger events.
				Options: mautic.lead_post_save_new (fires when a new contact is created), mautic.lead_post_save_update (fires when an existing contact is updated), mautic.lead_points_change (fires when a contact’s point value changes), mautic.lead_post_delete (fires when a contact is deleted), mautic.lead_channel_subscription_changed (fires when a contact’s channel subscription changes), mautic.lead_post_save_identified (fires when a previously anonymous contact is identified), mautic.email_on_open (fires when an email is opened by a contact), mautic.email_on_send (fires when an email is sent to a contact), mautic.email_on_reply (fires when a contact replies to an email), mautic.form_on_submit (fires when a Mautic form is submitted), mautic.page_on_hit (fires when a tracked page is visited by a contact), mautic.point_on_trigger (fires when a point trigger action is executed), mautic.campaign_on_trigger (fires when a campaign event is triggered), mautic.stage_on_change (fires when a contact’s stage changes), mautic.webhook_kill (fires when a webhook is killed (disabled) by Mautic due to excessive failures)
Events Order	options	No	ASC	Order direction for queued events in one webhook delivery. Can be “ASC” (oldest first) or “DESC” (newest first).
				Options: ASC, DESC

Output Data

Each Mautic delivery produces one output item:

• _trigger — always mautic_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the Mautic event name, taken from the delivery’s event header or from the first mautic.* key in the body; unknown when neither is present

The raw Mautic body is merged in at the top level. Mautic keys that body by event name, so a contact-creation delivery arrives as a mautic.lead_post_save_new array of records — reference it downstream by expression, e.g. {{ $json["mautic.lead_post_save_new"][0].contact.id }}. Because Mautic can queue several events into one delivery, use Events Order to control whether the oldest or newest entry comes first.

Example Configuration

Fire when a contact is created, oldest queued event first:

{
  "type": "mautic_trigger",
  "parameters": {
    "authentication": "credentials",
    "events": ["mautic.lead_post_save_new"],
    "eventsOrder": "ASC"
  }
}

Watch every contact-lifecycle change:

{
  "type": "mautic_trigger",
  "parameters": {
    "authentication": "credentials",
    "events": [
      "mautic.lead_post_save_new",
      "mautic.lead_post_save_update",
      "mautic.lead_post_delete",
      "mautic.lead_points_change"
    ],
    "eventsOrder": "ASC"
  }
}

Handle form submissions and email engagement, newest event first:

{
  "type": "mautic_trigger",
  "parameters": {
    "authentication": "oAuth2",
    "events": [
      "mautic.form_on_submit",
      "mautic.email_on_open",
      "mautic.email_on_reply"
    ],
    "eventsOrder": "DESC"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

This tool receives Mautic marketing automation events via webhooks. It is ideal for initiating workflows when specific events like contact creation, form submissions, or email interactions occur in Mautic. The tool produces the raw POST body from Mautic as its output payload.