- 1. Getting Started
- 2. What's New
- 3. Dashboard
- 4. Contacts
- 5. Components
- 6. Channels
- 7. Campaigns
- 8. Reports
- 9. Points
- 10. Stages
- 11. Categories
- 12.1. Citrix Plugins
- 12.2. Clearbit
- 12.3. ConnectWise
- 12.4. FullContact
- 12.5. Gmail
- 12.6. Hubspot CRM
- 12.7. iContact
- 12.8. Mailchimp
- 12.9. Microsoft Dynamics CRM
- 12.10. Microsoft Outlook
- 12.11. Pipedrive
- 12.12. Salesforce CRM
- 12.13. Sugar CRM
- 12.14. Twitter
- 12.15. vTiger CRM
- 12.16. Zapier
- 12.17. Zoho CRM
- 12.18. Social login
- 12.19. Field Mapping
- 12.20. Integration Testing
- 13. Use Cases
- 14. Cron Jobs
- 15. SAML SSO
- 16. Queue Support (RabbitMQ/Beanstalkd)
- 17. Themes
- 18. Translations
- 19. Tips & Tricks
- Published with GitBook
Mautic Zapier Integration
This integration integrates any Mautic instance with 1.100+ third party web services via the Zapier web automation service.
- Mautic version 2.9.0 or newer with SSL - basic authentication requires HTTPS to be secure.
- Zapier account. Free or Paid. View Zapier pricing.
There is no need to install any additional plugin to your Mautic instance. Zapier works with the API and webhooks already available within Mautic. This Zapier integration use Basic Authentication to access Mautic API. It is disabled by default so enable this first.
- Open the admin menu
- Go to Mautic's global configuration
- Go to API Settings
- Set API enabled? to Yes.
- Set Enable HTTP basic auth? to Yes.
- Save the configuration.
Zapier will be able to create actions and triggers with your Mautic installation.
Sign up for a Zapier account
- Go to the Zapier website.
- Select the "Sign Up for Free" button.
Or log into your existing Zapier account.
Setup and configuration
The configured Zapier integrations are called Zaps. The main types of Zaps are Triggers and Actions.
- Triggers send data about some actions that happen in Mautic in realtime to Zapier. Zapier then transforms the data and sends it to the next app you have configured in the Zap.
- Actions send data from some other app into Mautic.
- [x] New Contact - contains contact info and field values
- [x] Updated Contact - contains contact info and field values
- [x] Contact Points Changed - contains contact info, point value and field values
- [x] Email Viewed - contains contact info and field values and info about the email
- [x] New Page Hit - contains contact info and field values, info about the page hit and the page itself
- [x] New Form Entry - contains contact info and field values, info about the form and about the submission including submitted values
- [x] Create or Update Contact
1. Find Mautic integration
When you click on Make a Zap! button, search for Mautic. You may see some unofficial Mautic integrations there. We recommend to use this one. It will always be called "Mautic (2.1.0)". Of course the version number will change in time. The latest version number is available within each changelog at https://github.com/mautic/mautic-zapier/releases.
If you want some inspiration or speed up the process of creating a Zap use preconfigured Mautic Zap templates:
2. Choose a Trigger or Action
At this point choose which Trigger or Action you need. Each trigger will get you some data about the Mautic event (page hit, email viewed, form submitted) and about the contact who did the event.
3. Authorize Mautic instance
Once you choose to use Mautic integration you'll need to authorize your Mautic to it. Mautic use basic auth as mentioned earlier. So all you need is a Mautic user credentials and URL of where your Mautic lives. It's recommended to create a new user for Zapier which will have some advantages:
- Giving a third party app credentials to your Mautic is a security risk. If something happens you simply delete this special Zapier user and your admin user will be safe.
- You will see what contacts were created by Zapier simply by looking at the created by user.
4. Select an item for Triggers
Triggers will ask you to choose which entity you want to record events about. This step is required for Form Submission trigger because every form has different form fields, but it's optional for others. If you skip this step for for example Page Hits trigger Zapier will process all page hit events.
Zapier will let you test the integration you just configured.
5. Map fields
Now map the Mautic fields to the fields of the other app. In the image below is an example of mapping Mautic fields from Mautic's New Form Entry Trigger to GMail's Send Email Action.
That's it! Now if a contact submits a Mautic form the contact gets an email. Okay, so Mautic can do that on its own, but you get the general idea.
How does this work
This happens when you create a new action or trigger at Zapier.
- Zapier creates a new webhook via Mautic API at your Mautic instance specifically for this one Zap. Mautic will then send all events related to the trigger or action type to Zapier.
- Zapier lets you map Mautic fields to the fields of the integration you want to connect to Mautic.
- Once you make your Zap active Mautic will start receiving data (in the case of actions) and sending data (in the case of triggers).
Even this integration is developed as an open source software as is usual with Mautic community. Learn more at https://github.com/mautic/mautic-zapier.