Skip to main content

We use a core system that has an API but no web hooks, but we can configure customer trigger and automation emails. We are using these feed into Zapier’s email parser to trigger web hooks (and other actions).

We are having a lot of issues with incorrect parsing, whereby the parse output is pulling in other data (inc. fields that aren’t even physically adjacent in the email).

I’ve tried creating new inboxes, reporting the outputs as inaccurate and re-mapping. I’ve left the default settings for body source and parser engine - not sure if I should switch based on our data structure, or just go out and pay for a different email parser?

  • Body Source - Use the best body content available
  • Parser Engine - Best Match (v1 + 2 recommended)

 

 

See example of incorrect Parse Output Contactlast below being pulled in Zapier:

 

 

In terms of the email trigger, we are using a very simple format, with each piece of data on its own line. For example: 

Reservation Number: {{reservation.id}}

Reservation ID: {{reservation.uuid}}

 

This is was the HTML looks like, for example: 

<p>Reservation Number: {{reservation.id}}</p>
<p>Reservation ID: {{reservation.uuid}}</p>
<p>Reservation URL: https://lodgeur.trackhs.com/pms/reservations/view/{{reservation.id}}</p>
<p>Reservation Type: {{reservation.type}}</p>
<p>Unit Name: {{unit.name}}</p>
<p>Unit Short Name: {{unit.shortName}}</p>
<p>Unit ID: {{unit.id}}</p>
<p>Unit Type Name: {{unitType.name}}</p>
<p>Unit Type Short Name: {{unitType.shortName}}</p>
<p>Start Date: {{formatDate reservation.checkin "medium"}}</p>
<p>End Date: {{formatDate reservation.checkout "medium"}}</p>
<p>Nights: {{reservation.nights}}</p>
<p>Reservation Status: {{reservation.status}}</p>
<p>Contact ID: {{contact.id}}</p>
<p>Guest Full Name: {{contact.name}}</p>
<p>Guest First Name: {{contact.first}}</p>
<p>Guest Last Name: {{contact.last}}</p>

 

And this is how it’s appearing in Email Parser (in this example, the field unittypename is returning half a dozen other fields in the same payload:

 

 

To make matters even more confusing, it’s not the same parsing output errors each time 

Hi @sebbie 

From experience the Email Parser by Zapier is not as reliable or as robust as other email parsing options.

Here are other more robust options for doing email parsing:

 


@Troy Tessalone for the sake of my own mental health, I really do think I will need to switch to a paid option! 😂

I’d bookmarked Parsio and Mailparser in the past - any personal preference for reliability / ease of use?

I’ll probably try both since I have so little faith in email parsers after the Zapier experience!

Thanks for sharing the ChatGPT option - a little more technical, but could be worth a shot. 


@sebbie 

I like Mailparser.

Mailparser: https://zapier.com/apps/mailparser/integrations#triggers-and-actions

Parsio: https://zapier.com/apps/parsio/integrations#triggers-and-actions


Reply