Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi

Is there a way to tell the Email Parser to ignore all subsequent text that appears after a specific value in an email?

Our Outlook attaches long legal disclaimers after the “yours ...” salutation, that I do not need to parse, and in some cases causes the wrong value to be extracted.

I’m currently sending value pairs like:

Firstname: John

Lastname: Bloggs

Email: j.bloggs@anytown.com

 

but the parser can be hit and miss.

I can send a more rigid form like XML or JSON or pipe delimited, would be interested in learning if there is a 100% guaranteed way to assure the email body data is extracted properly from an email.

 

Many thank

 

 

 

@KieranC-BL 

Unfortunately not - the Zapier Parser aways examines the whole body text of the email. There isn’t a way to apply more nuance.

Would you like me to flag this post so someone from the Zapier team can add your vote to a feature request?

Yeah thanks Andrew, I think that would be a good feature.

Hi @KieranC-BL 

Consider using a more robust email parser such as Mailparser: https://zapier.com/apps/mailparser/integrations#triggers-and-actions

 

Alternatives, a more advanced approach would be to use a Code step with custom code to parse out the desired data points.

Hi @KieranC-BL!

I created that feature request for you and added your vote for it :)

 

Thanks for the feedback, we’ve opted for Parseur in the end as it provides an excellent interface into Zapier and allows us to create concise templates that are constrained by specific values (which is neat). Zap and Parseur working nicely together now.

Terms & Conditions