Check for valid Mautic contact email

For Mautic, this workflow checks if a contact's email is valid, identifying suspicious emails and sending alerts to Slack. It automates the process of validating email addresses for existing contacts, ensuring better deliverability and reducing the risk of spam or invalid entries.

7/8/2025
6 nodes
Medium
manualmediummautictriggeritemlistsonesimpleapislacklogicconditionalcommunicationnotification
Categories:
Communication & MessagingManual TriggeredMedium WorkflowMarketing & Advertising Automation
Integrations:
MauticTriggerItemListsOneSimpleApiSlack

Target Audience

This workflow is ideal for:
- Marketing Teams: Who need to ensure that new contacts in Mautic have valid email addresses to maintain a clean database.
- Sales Teams: Looking to avoid engaging with potential leads that may have suspicious or invalid emails.
- Data Analysts: Who require insights into the quality of email addresses collected through forms or campaigns.
- Customer Support Teams: Aiming to reduce issues related to communication failures due to invalid email addresses.

Problem Solved

This workflow addresses the challenge of identifying and managing new contacts with potentially suspicious email addresses. By validating emails upon creation, it ensures that:
- Invalid emails do not clutter the database.
- Disposable emails are flagged to prevent future communication issues.
- Domain validity is checked to maintain the integrity of contact lists.

Workflow Steps

  • Manual Trigger: The workflow begins when a new contact is identified in Mautic through a manual trigger.
    2. Check for Existing Contacts: It checks if the contact is not new by evaluating the mautic.lead_post_save_new variable. If the contact is new, it proceeds to the next step.
    3. Extract Contact Information: The workflow extracts relevant information from the new contact data, focusing on email and other essential fields.
    4. Email Validation: The extracted email address is validated using the One Simple API to assess its deliverability, domain validity, and whether it is disposable.
    5. Check for Suspicious Emails: If the email is flagged as suspicious based on the validation results (not good deliverability, invalid domain, or disposable), it triggers the next step.
    6. Send Notification to Slack: A notification is sent to a specified Slack channel containing details of the suspicious contact, including their name, email, and a link to their Mautic profile.

    • Customization Guide

    Users can customize this workflow by:
    - Modifying Conditions: Adjust the conditions in the 'If the email is suspicious' node to include or exclude specific criteria based on business needs.
    - Changing Notification Details: Customize the message sent to Slack by altering the text in the 'Send to Slack' node to include additional information or formatting.
    - Integrating Additional Services: Add more integrations or nodes to enrich the workflow, such as sending alerts via email or integrating with CRM systems.
    - Adjusting Trigger Settings: Change the manual trigger to an automatic trigger based on different events in Mautic, depending on how contacts are managed.