@escopecz I reached out to Mautic.com support but got no reply. I have just tried again, maybe I will get a response this time
A bit of a heads up to anyone using this currently. I have simplified the lead field names, it does mean that you will likely need to rebuild many of your zaps but Zapier will send you error emails if there are any problems
@zpetterd thx a lot for this integration, it works for me from mautic ( trigger) to Pipeliner CRM ( action app)
As @pramodgeorge I’m also trying to get a lead from a certain stage in Pipeliner CRM ( trigger) to a lead list in Mautic ( Action)
Can’t get that to work, I read this is because Mautic needs lead ID…any chance this wil eventually be solved? or is their another solution?
Thx
Peter
@peterd and @pramodgeorge my best recommendation is to include the leads Mautic id in a custom field in your CRM and then use that field later on in the Add to a list action in Zapier.
While Zapier has search to zaps, there is no way of sensibly doing the search with the Mautic API. Currently it would mean dumping out all of your leads(13,000 in our case) then doing the search on that data.
We use passing through the Mautic lead id with Highrise to do exactly what you are talking about.
Zsc
@zpetterd thx! one step further again 
Once again I’ve updated the integration, the callback URI is now https://zapier.com/dashboard/auth/oauth/return/App33579API/ for anyone newly setting it up
The invite link is also https://zapier.com/developer/invite/33579/8f3ef06e001c138c48bfa3a266cfb618/
@zpetterd Works for me so far. Any plans to implement lead listing with filtering?
@pschrammel has pointed out that the Mautic API supports search (I’m not sure how I missed it before). But we now have search!!
As such the invite URL is now https://zapier.com/developer/invite/37497/89d048c630989b33ba0b8bd3b13647af/
and callback URI https://zapier.com/dashboard/auth/oauth/return/App37497API/
@zpetterd clicking on the callback URI gives me a 404 error, why is that? From what i understood reading this thread the callback URI changes A LOT but i don’t know why changes and who changes that URI. Can someone please explain that?
@marzio You need to click on the invite link, the callback URI is entered into Mautic and expects certain data to be passed through, hence the 404.
As the integration is still in beta Zapier doesn’t keep the invite or callback links consitent when a update is released. Your account which you setup before the update will keep working though.
@zpetterd thanks for your answer. Let me tell you that there is something that i don’t understand. Why you, an user, are working on a Zapier integration that Mautic developers should working on? This is something that honestly scares me a lot because what if you simply don’t have time to keep working on the Zapier integration?
@marzio Mautic is a open source project and the core team are happy to have others helping with the development. I created this as we needed it to do what we need to and then I have added more to it based off of requests by the community. Honestly it won’t just be left it will be passed onto thr core development team, just need to work out the logistics of sharing the development account which is happening at the moment. Unless the whole API is rewritten there is no reason that it would magically stop working. If you have a look on GitHub you will realise that there is quite a few people contributing to Mautic who aren’t part of the core team
Hi,
I just tried generating my API keys, used the callback URI as
https://zapier.com/dashboard/auth/oauth/return/App37497API/
However I got this error message:
{"error":"redirect_uri_mismatch","error_description":"The redirect URI provided does not match registered URI(s)."}Has the URI changed?
Also, will my zap stop working next time the URI changes?
Cheers
Never mind, I just realised that the callback URL is on the oAuth screen. Duh!
… however, my question still remains. Will the zap stop working next time the callback URL changes?
… on a different note. I can only use the NEW LEAD trigger. The other two (New Lead with Email, etc) return an error on Zapier. Is anyone else getting this too?
Ah, those aren’t really needed anymore thanks to webhooks in Mautic. The New lead with Email trigger should still work but was a workaround, the better way to do it is to use a New form submission trigger which adds the lead to wherever you need to.
Your zap will still keep working, it is just needed for the initial authentication.
@zpetterd what should i select in the Mautic app in Zapier that when a trigger happens Mautic will add a new lead to a selected list or if the lead is already present will modify informations about that lead (like changing tags or removing/adding to another list)
The Add to list action… Adding tags isn’t currently poasible but I will look into it
@zpetterd if you could add tags that would be great! I would love to have only a list for product A with tags for prospects and tags for customers so i can send emails based on those tags.
The ideal scenario would be that when a trigger happens Mautic will add a tag (customer product A) and remove a tag (prospect product A, if this tag is present)
Do you think it will be possible to achieve something like that?