Send parsed lead emails to Zapier: add to your CRM and get a text
· SyncYak team
A lead email lands in your inbox while you are at a showing. By the time you open it, copy the phone number into your CRM and call back, the lead has probably talked to someone else. The email itself is fine. The slow part is everything you do by hand afterward.
Zapier can do that part for you, but only if it receives clean fields. Zapier's own email trigger gives you the raw message, and a portal notification is a wall of text with a name, a phone number and a property address buried in it. This guide shows how to parse the email first, then hand named fields to a Zap that creates the contact and sends you a text.
Why parse before you automate
A Zap that starts from a raw email has to guess where the phone number is. Every portal formats its notification differently, and they change the layout from time to time. When the layout changes, a Zap that relied on text positions fills your CRM with half-empty contacts, and you find out days later.
Parsing separates two jobs. One tool reads the email and returns fields such as full_name, email, phone and property_address. The Zap only has to move those fields from A to B. When a portal redesigns its email, you fix one template, not every Zap.
What you need
- A Zapier account on a plan that includes Webhooks by Zapier, which provides the Catch Hook trigger.
- A SyncYak Parse inbox. The free plan includes 100 emails a month and 2 inboxes, which is enough to build and test this.
- Lead emails from a source with a ready-made template. Parse covers Zillow buyer and seller leads, Zillow mortgage leads, Realtor.com, IDX website registrations, CINC, BoomTown, Follow Up Boss, Velocify, Firepoint, eLead Network and paid social lead forms. A catch-all template handles the rest.
- A CRM that Zapier can write to, and a way to send a text, such as an SMS action or a Slack message to your phone.
Step 1: Start the Zap with Catch Hook
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger, with the event Catch Hook. Zapier shows you a URL. Copy it. You will paste it into your Parse inbox in a moment.
Leave the Zap open, because the next step sends it a test lead.
Step 2: Create the inbox and pick a template
In Parse, create an inbox and choose the template for the source you want to start with. Every inbox has an address on parse.syncyak.com, and sub-addresses reach the same inbox, so you can use one address per source:
[email protected]
[email protected]
Add the destination: choose Zapier and paste the Catch Hook URL. Make and n8n work the same way if you prefer them.
Then forward your lead emails to the inbox. In Gmail or Outlook, a filter on the sender forwards new portal emails automatically, and your own inbox keeps its copy. You can also set the Parse address as the address the portal sends to.
Step 3: Send a real lead and look at the fields
Forward one recent lead email. Parse reads it and posts the result to your Zap. Back in Zapier, click Test trigger. You should see the fields arrive under fields, named the way the template names them:
{
"event": "parse.message.parsed",
"template": { "name": "Zillow buyer enquiry" },
"fields": {
"full_name": "Maria Gonzalez",
"phone": "3055550142",
"property_address": "18 Bayview Ave"
}
}
Check each field against the original email. If a field is empty, open the template in Parse, look at what each rule extracted from the last messages, and adjust it before building the rest of the Zap. Every email is kept for your plan's retention period whether it parsed or not, so you can replay a message after fixing the template.
Step 4: Add the CRM and text actions
Now the Zap has real data to map.
- Create the contact. Add an action for your CRM that creates a contact or a lead. Map
full_name,emailandphoneto the matching CRM fields. Putproperty_addressin a note or a custom field so you can see which listing the lead asked about. - Text yourself. Add an SMS or Slack action. A message that works on a lock screen is short: the lead's name, the phone number, the property. For example, "New lead: Maria Gonzalez, 3055550142, 18 Bayview Ave".
- Turn the Zap on.
Keep the text free of anything you would not want on a locked phone, and keep the CRM contact as the record of truth. The text is only the nudge.
Make the Zap handle more than one source
Once the first source works, add the others without building new Zaps:
- Create one Parse inbox per source, or use sub-addresses on one inbox, and point each at the same Catch Hook URL.
- Because the templates use the same field names, a Zillow lead and a Realtor.com lead look identical to the Zap.
- Add a Zapier Filter or a field for the source if you want to treat portals differently, for example to tag the CRM contact with where it came from.
If your team has several agents, a lookup can add the right agent before the lead is delivered. Parse finds the row of a second Google Sheet whose column matches a parsed field, such as a zip code, and copies the columns you pick into the lead. Your Zap then receives the agent's name or email along with the lead. Lookups start on the Hobby plan. The lead routing for brokerages page walks through that setup.
Keep it reliable
- Watch the monthly count. The free plan covers 100 emails a month. If you outgrow it, check the plans on the Parse page for the tier that fits.
- Test after any portal change. If a portal changes its email design, the catch-all template still delivers name, email and phone while you update the specific template.
- Check Zapier's task history. If a Zap run fails, Parse retries failed deliveries, and the Zap history shows which lead was affected.
How SyncYak helps
Parse does the part Zapier is not built for: reading a lead email and returning named fields from templates you can edit. It then delivers each parsed email to a Zapier Zap, a Google Sheet row or your own webhook, and keeps the history for your plan's retention. For the full setup, see the email to Zapier, which covers the same flow.
Create a free account at /signup, forward one lead email to a new inbox, and build the Zap from the fields you see arrive.