Mautic n8n integrationAutomate Mautic with n8n.

Puts a contact that already exists in Mautic into one of its campaigns, and the steps of that campaign start running for this person.

• Contact ID: the identifier of the contact inside Mautic, most often passed with an expression such as {{ $json.id }} from the node that just created or read it.
• Campaign Name or ID: required as well. Campaigns show up in a dropdown, and an expression supplies the ID when the campaign depends on the item being processed.

Ends a contact's membership in a campaign. The contact stays in the instance with its history, only the campaign stops running its steps for them.

• Contact ID: who leaves. A workflow usually carries this value from an earlier step instead of a manual entry.
• Campaign Name or ID: which campaign they leave, picked in the list or resolved by expression.

A company record appears in Mautic, ready to gather the contacts who work there. No field is marked required, so fill Company Name unless unnamed records are your thing.

• Company Name: the name the company is known by in Mautic.
• Additional Fields: 12 optional entries, among them Company Email, Phone, Website, Industry Name or ID, Annual Revenue and Number of Employees, plus Custom Fields for what your instance defines itself.
• Simplify: on, n8n returns a trimmed version of the response instead of the raw API payload.

Removes one company from the instance. n8n does not flag Company ID as required here, yet the operation has no target without it.

• Company ID: the ID of the company to delete, usually carried over from a lookup or from a list of duplicates.
• Simplify: keeps the returned record short when the workflow only needs a confirmation.

Reads a single company and hands its data to the next node. Nothing is written back, which makes it the safe operation to test a credential with.

• Company ID: the record to read. An expression keeps it dynamic when the ID comes from the previous item.
• Simplify: the short response is usually enough, so switch it off only when a later node needs a field the simplified version drops.

The listing operation for companies: one item per company, ready to loop over in the rest of the workflow.

• Return All: switched on, n8n walks the pages of the Mautic API until every company is returned; switched off, Limit caps how many companies come back.
• Search: a string or a Mautic search command, to filter the companies before they reach n8n rather than after.
• Order By Name or ID and Order Direction: the column to sort on, and asc or desc.

Writes new values onto a company that already exists. Only the fields filled in the node travel to Mautic, the rest of the record is left alone.

• Company ID: the company to update, taken from a previous company.getAll or from your own database.
• Update Fields: 13 entries, the same ground as creation plus Company Name, so a rename is a single call.
• Overwrite With Blank: on, empty values are written to the fields; off, they are skipped, which protects data already in place.

Two IDs, one link: the contact is attached to the company, which is how Mautic knows who works where.

• Contact ID: the ID of the contact to attach.
• Company ID: the ID of the company. Neither field is marked required in the interface, so both come from earlier nodes in practice.

The link goes away, both records stay. That matters when a relationship changes and the history should not.

• Contact ID: the person to detach.
• Company ID: the company they are detached from, given as an ID and never as a name.

Creates the contact in Mautic and returns it. Two ways to fill it in: field by field, or as a raw JSON body when the data already arrives shaped.

• Email, First Name, Last Name: the identity fields, filled from the incoming item.
• Primary Company Name or ID: links the new contact to a company straight away.
• JSON Parameters and Body: switch the first on and the contact parameters travel as JSON.
• Additional Fields: 23 entries, including Tag Names or IDs, Stage Name or ID, B2B or B2C, Prospect or Customer and Custom Fields.

Erases a contact from Mautic. The node asks for no confirmation, so a wrong ID deletes the wrong person.

• Contact ID: the only field that matters here, and the one to double check before the workflow is activated.

Mautic scores contacts with points, and this operation moves that score up or down from a workflow, on the signals your own tools produce.

• Contact ID: whose score changes.
• Action: add or remove, the direction of the change.
• Points: how many points that action applies.

Flags a contact as not to be contacted on a given channel, or lifts that flag. Consent lives in Mautic, and this operation is how a workflow respects it.

• Channel: required, email or sms.
• Action: add puts the contact on the list, remove takes them off.
• Contact ID: the contact concerned.
• Reason To Do Not Contact: Unsubscribed, Bounced or Manual, with Comments for the detail a colleague will read six months later.

Fetches one contact and its fields. This is the usual first step after an event tells the workflow that someone did something.

• Contact ID: the contact to read, generally an expression pointing at the identifier the previous node carries.
• Options: Minimal returns the entity without its extra lists, and RAW Data returns the full API response instead of the field values alone.

Returns the contacts of the instance as a list of items. Most exports and most audits of a Mautic base start here.

• Return All: on, n8n follows the pagination of the API to the end; off, Limit decides how many contacts come back.
• Search: a Mautic search command narrows the list, which beats filtering thousands of items downstream.
• Published Only: keeps only the entities currently published.

Sends a campaign email that already exists in Mautic to a single contact. The email stays the one the marketing team built; the workflow only decides who gets it and when.

• Campaign Email Name or ID: required, chosen among the campaign emails of the instance or resolved by expression.
• Contact ID: required as well, the single recipient of that send.

Updates an existing contact. Update Fields is the widest collection of the node, 31 entries, so most enrichment work ends up here.

• Contact ID: the contact to modify.
• Update Fields: identity fields plus Tag Names or IDs, Stage Name or ID, Owner ID, Has Purchased, Last Active and Custom Fields, among others.
• JSON Parameters: on, the contact parameters travel in Body as JSON, which suits a payload already built upstream.

Files a contact into a segment. Segments are the lists Mautic sends to, so this operation turns a decision taken in a workflow into an audience.

• Contact ID: required, the contact joining the list.
• Segment Name or ID: required, picked among the segments of the instance or given as an ID with an expression, handy when the segment depends on a field of the item.

Takes the contact out of the list. Running it before an add keeps the same person from sitting in two competing segments at once.

• Contact ID: required, the contact to pull out.
• Segment Name or ID: required, the segment they leave.

One field, one send: the segment email goes out to the whole list it targets. This is the batch counterpart of the single contact send.

• Segment Email Name or ID: required, and the only parameter. Choose the segment email from the list, or pass its ID with an expression when the send is decided upstream.