MAUTIC n8n INTEGRATION: AUTOMATE MAUTIC WITH N8N

This action allows you to send a pre-configured segment email directly from your n8n workflow. It's perfect for triggering targeted email campaigns based on external events or conditions that Mautic alone couldn't detect.

Key parameters: Credential to connect with (required dropdown for Mautic account selection), Resource (set to "Segment Email"), Operation (set to "Send"), and Segment Email Name or ID to specify which segment email to dispatch.

Use cases: Trigger a promotional email when a specific event occurs in another app, send follow-up emails based on actions tracked outside Mautic, or coordinate email sends with your broader automation workflows.

This action removes a contact from a specific segment in Mautic. It's essential for maintaining clean, relevant segments by automatically removing contacts who no longer meet certain criteria.

Key parameters: Credential to connect with (required), Resource (set to "Contact Segment"), Operation (set to "Remove"), Contact ID (required numeric identifier), and Segment Name or ID (required to specify the target segment).

Use cases: Remove contacts from a "Hot Leads" segment when they haven't engaged in 30 days, automatically unsegment contacts who unsubscribe or request removal, or clean up segment membership when contacts are updated in your CRM.

This action adds a contact to a specific segment in Mautic. Segment membership drives much of Mautic's automation logic, making this action crucial for targeted marketing.

Key parameters: Credential to connect with (required), Resource (set to "Contact Segment"), Operation (set to "Add"), Contact ID (required, can be fixed value or expression), and Segment Name or ID (required to identify the target segment).

Use cases: Add new leads to a "Needs Nurturing" segment when they sign up, segment contacts based on purchase behavior tracked in your e-commerce platform, or automatically categorize contacts based on form responses or survey answers.

This action updates an existing contact's information in Mautic. It's perfect for keeping your Mautic database synchronized with data from other systems.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Update"), Contact ID (required), JSON Parameters toggle, Update Fields (specify which fields to modify), and Options for additional configuration.

Use cases: Sync contact data changes from your CRM to Mautic in real-time, update contact scores or tags based on external engagement data, or keep contact information consistent across your entire tech stack.

This action sends a campaign email to a specific contact. Unlike segment emails, this targets an individual contact directly—perfect for triggered, personalized communications.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Send Email"), Campaign Email Name or ID (required to select the email template), and Contact ID (required recipient identifier).

Use cases: Send a welcome email immediately when a contact is created from an external form, trigger transactional emails based on purchase events, or send personalized follow-ups based on actions in other applications.

This action retrieves multiple contact records from Mautic. It's essential for bulk operations, reporting, or syncing contacts to other systems.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Get Many"), Return All toggle (to override limit), Limit (maximum number of contacts, default 30), and Options to add filters or sorting.

Use cases: Export contacts to a spreadsheet or external database regularly, sync all contacts with a specific tag to another marketing platform, or build reports by pulling contact data into analytics tools.

This action retrieves detailed information about a single contact by their ID. It's perfect for lookup operations or enriching data in your workflows.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Get"), Contact ID (required unique identifier), and Options for customizing the response.

Use cases: Look up contact details before making decisions in your workflow, enrich data from other systems with Mautic contact information, or verify contact existence before performing other operations.

This action manages a contact's "Do Not Contact" (DNC) status for specific channels. It's crucial for compliance and respecting contact preferences.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Edit Do Not Contact List"), Contact ID (required), Action (choose "Add" or "Remove"), Channel (select communication channel like "Email"), and Additional Fields for optional comments or reasons.

Use cases: Automatically add contacts to DNC when they unsubscribe via an external system, remove contacts from DNC when they re-subscribe, or sync opt-out preferences from your CRM or preference center.

This action modifies a contact's point score in Mautic. Points drive lead scoring and can trigger automated campaigns, making this action powerful for engagement-based automation.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Edit Contact Points"), Contact ID (required), Action (choose "Add" or "Subtract" points), and Points (number of points to modify).

Use cases: Award points when contacts engage with external content (webinars, resources), deduct points for negative behaviors tracked outside Mautic, or synchronize lead scores across multiple marketing platforms.

This action permanently deletes a contact from Mautic. Use it carefully—deletion is irreversible.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Delete"), Contact ID (required), and Options for additional delete operation settings.

Use cases: Automatically remove contacts who request GDPR erasure, clean up test contacts after workflow testing, or delete duplicate contacts after a merge operation.

This action creates a new contact in Mautic. It's fundamental for lead capture workflows that funnel contacts from external sources into your marketing automation.

Key parameters: Credential to connect with (required), Resource (set to "Contact"), Operation (set to "Create"), Email (required contact email address), First Name (optional), Last Name (optional), Primary Company Name or ID (optional), Position (optional), Title (optional), and JSON Parameters toggle.

Use cases: Create contacts from form submissions (Typeform, Gravity Forms, etc.), add leads from webinar registrations or event sign-ups, or sync new customers from your e-commerce platform like WooCommerce.

This action removes the association between a contact and a company in Mautic. It doesn't delete either record—just severs the relationship.

Key parameters: Credential to connect with (required), Resource (set to "Company Contact"), Operation (set to "Remove"), Contact ID (required), and Company ID (required to identify which company to disassociate from).

Use cases: Remove contacts from companies when they change employers, clean up incorrect company associations, or reorganize contacts during CRM data cleanup.

This action associates a contact with a company in Mautic. Company associations are valuable for B2B marketing and account-based strategies.

Key parameters: Credential to connect with (required), Resource (set to "Company Contact"), Operation (set to "Add"), Contact ID (required), and Company ID (required to specify which company to link to).

Use cases: Associate contacts with their employer when company data arrives from your CRM, build account-based contact groups automatically, or maintain accurate B2B contact hierarchies.

This action updates an existing company record in Mautic. Keep company data current to ensure accurate account-based marketing.

Key parameters: Credential to connect with (required), Resource (set to "Company"), Operation (set to "Update"), Company ID (required), Simplify toggle for API response formatting, and Update Fields to specify which company attributes to modify.

Use cases: Sync company data changes from your CRM to Mautic, update company attributes based on external data enrichment, or keep company information consistent across platforms.

This action retrieves multiple company records from Mautic. Use it for bulk operations, exports, or syncing company data.

Key parameters: Credential to connect with (required), Resource (set to "Company"), Operation (set to "Get Many"), Return All toggle, Limit (maximum records to return, default 30), Simplify toggle for response format, and Additional Fields for filters or sorting.

Use cases: Export all companies to an external database, sync company lists with your CRM or sales platform, or build company-level reports.

This action retrieves a single company's details by ID. Essential for lookup operations in company-centric workflows.

Key parameters: Credential to connect with (required), Resource (set to "Company"), Operation (set to "Get"), Company ID (required unique identifier), and Simplify toggle for simplified response formatting.

Use cases: Look up company details before processing related contacts, enrich workflows with company data from Mautic, or verify company existence before performing other operations.

This action permanently deletes a company from Mautic. As with contact deletion, use this carefully.

Key parameters: Credential to connect with (required), Resource (set to "Company"), Operation (set to "Delete"), Company ID (required), and Simplify toggle for simplified response.

Use cases: Remove duplicate company records after cleanup, delete test companies after workflow testing, or clean up companies merged into other records.

This action creates a new company in Mautic. Essential for B2B workflows where company records drive segmentation and targeting.

Key parameters: Credential to connect with (required), Resource (set to "Company"), Operation (set to "Create"), Company Name (required), Simplify toggle for response formatting, and Additional Fields to add extra attributes like address, industry, etc.

Use cases: Create companies from CRM deal data, add companies when new contacts mention their employer, or build company records from enrichment services like Clearbit.

This action removes a contact from a campaign in Mautic. Use it to stop contacts from receiving campaign communications.

Key parameters: Credential to connect with (required), Resource (set to "Campaign Contact"), Operation (set to "Remove"), Contact ID (required), and Campaign Name or ID (required to specify which campaign to remove from).

Use cases: Remove contacts who convert before campaign completion, stop campaigns for contacts who request it, or clean up campaign membership based on external signals.

This action adds a contact to a campaign in Mautic. Campaign enrollment is a core marketing automation function, driving nurturing sequences and automated communications.

Key parameters: Credential to connect with (required), Resource (set to "Campaign Contact"), Operation (set to "Add"), Contact ID (required), and Campaign Name or ID (required to identify the target campaign).

Use cases: Automatically enroll leads in nurturing campaigns when they meet certain criteria, add contacts to campaigns based on behavior tracked in other apps, or trigger campaign enrollment from CRM stage changes. Our n8n agency can help you build these advanced workflows.