Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Mautic

Open-source marketing automation software

CategoryMarketing
Authenticationcustom
Version0.6.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Mautic with Flows360

Open-source marketing automation software

Use the Mautic connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 4 triggers.

Available actions

  • Create Contact
  • Search Contact
  • Update Contact With Contact Id
  • Create Company
  • Search Company
  • Update Company With Contact Id
  • Custom API Call

Available triggers

  • Contact Updated
  • Contact Company Subscription Change
  • Contact Channel Subscription Change
  • New Contact

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Mautic
  • Package: @activepieces/piece-mautic@0.6.0
  • Exact artifact digest: sha256:c798bae725ed272f319e6376f696add0406da82641d8585c63a34e1109928b2a
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Contact (create_mautic_contact), Creates a new contact in Mautic CRM Classification: read.
  • Search Contact (search_mautic_contact), Search for a contact in Mautic CRM Classification: read.
  • Update Contact With Contact Id (update_mautic_contact), Update a contact in Mautic CRM Classification: read.
  • Create Company (create_mautic_company), Creates a new company in Mautic CRM Classification: read.
  • Search Company (search_mautic_company), Search for a company in Mautic CRM Classification: read.
  • Update Company With Contact Id (update_mautic_company), Update a company in Mautic CRM Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Contact Updated, webhook.
  • Contact Company Subscription Change, webhook.
  • Contact Channel Subscription Change, webhook.
  • New Contact, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects11
Supported actions7
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Base URL Required
  • Username Required
  • Password Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Creates a new contact in Mautic CRM
Search Contact Yes No Search for a contact in Mautic CRM
Update Contact With Contact Id Yes No Update a contact in Mautic CRM
Create Company Yes No Creates a new company in Mautic CRM
Search Company Yes No Search for a company in Mautic CRM
Update Company With Contact Id Yes No Update a company in Mautic CRM
Custom API Call Yes No Make a custom API call to a specific endpoint
Contact Updated Yes No webhook trigger declared by the pinned package.
Contact Company Subscription Change Yes No webhook trigger declared by the pinned package.
Contact Channel Subscription Change Yes No webhook trigger declared by the pinned package.
New Contact Yes No webhook trigger declared by the pinned package.

Supported actions

Create Contact · Read

Creates a new contact in Mautic CRM

create_mautic_contact · Risk: low · Retry: safe

Inputs

  • fields · object · Required, List of all possible fields present
Search Contact · Read

Search for a contact in Mautic CRM

search_mautic_contact · Risk: low · Retry: safe

Inputs

  • fields · object · Required, List of all possible fields present
Update Contact With Contact Id · Read

Update a contact in Mautic CRM

update_mautic_contact · Risk: low · Retry: safe

Inputs

  • id · string · Required
  • fields · object · Required, List of all possible fields present
Create Company · Read

Creates a new company in Mautic CRM

create_mautic_company · Risk: low · Retry: safe

Inputs

  • fields · object · Required, List of all possible fields present
Search Company · Read

Search for a company in Mautic CRM

search_mautic_company · Risk: low · Retry: safe

Inputs

  • fields · object · Required, List of all possible fields present
Update Company With Contact Id · Read

Update a company in Mautic CRM

update_mautic_company · Risk: low · Retry: safe

Inputs

  • id · string · Required
  • fields · object · Required, List of all possible fields present
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Contact Updated · Webhook

Triggers when a contact is updated.

Inputs

  • name · string
  • description · string
Contact Company Subscription Change · Webhook

Triggers when a commpany is added or removed to/from contact.

Inputs

  • name · string
  • description · string
Contact Channel Subscription Change · Webhook

Triggers when a contact's channel subscription status changes.

Inputs

  • name · string
  • description · string
New Contact · Webhook

Triggers when a new contact is created.

Inputs

  • name · string
  • description · string

Setup

Setup

  1. Add the Mautic connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Base URL (base_url), required.
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-mautic@0.6.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 4 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Mautic connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-mautic@0.6.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com