Email parsing reads the lead emails you receive, pulls out the details (name, email, phone, what they asked for) and sends them into HubSpot as structured data. You need it when leads reach you by email from places that don't connect to HubSpot, such as listing sites, paid lead providers or partner platforms. Set up well, every emailed lead becomes a HubSpot contact and a deal, with its source recorded, and nobody has to copy anything by hand.
When you need email parsing with HubSpot
Parsing is the right fix when the lead arrives as an email and there is no better way to get it into HubSpot. Common cases:
- Listing sites and directories. Real estate portals, workspace marketplaces and industry directories often send each inquiry as a notification email rather than through an integration.
- Paid lead providers. Lead marketplaces in fields like staffing and commercial cleaning usually deliver leads by email in a fixed template.
- Partner and referral platforms. Partners who send prospects through a referral form or a standard email.
- Older website forms. Forms on a legacy site or third-party booking tool that only send an email to an inbox.
Without parsing, the lead sits in an inbox until someone copies it across. Leads that never get entered can't be counted, so you can't compare one source with another.
When you don't need it
Parsing is a workaround, so check for a direct route first.
- A native integration exists. If the lead source has a HubSpot app in the marketplace, or offers a webhook or API, use that instead. It is more reliable than reading emails.
- You control the form. If the form is on your own website, replace it with a HubSpot form, or make sure HubSpot collects the submissions directly. The data arrives clean and the source is tracked for you.
Your options for parsing lead emails
Zapier with Email Parser by Zapier
Email Parser by Zapier gives you a mailbox at an @robot.zapier.com address. You forward a sample email to it, then highlight the parts you want as data and label each one. Those labels become fields you can use in a Zap. From there, Zapier's HubSpot actions include "Find or Create Contact", "Create or Update Contact", "Create Deal" and "Find Deal".
It works well for emails that always follow the same layout, and less well for messy or changing formats. Zapier's own help notes that forwarded emails can parse badly.
Make with a custom mailhook
In Make, the Custom mailhook module generates an email address that starts a scenario whenever an email arrives. You forward lead emails to that address, use Make's text tools to pull out the fields, then use the HubSpot CRM modules such as "Search for Contacts", "Create or Update a Contact" and "Create a Deal".
Dedicated email parsers
Tools built only for parsing, such as Parseur and Mailparser, give you a dedicated address to forward emails to and then extract the data from the body or attachments. Mailparser works from parsing rules you set up. Parseur offers AI parsing that does not need a template, plus a point and click template editor if you prefer. Both send data on through Zapier, and Parseur also lists connectors for Make and Power Automate, as well as webhooks.
HubSpot's own options
HubSpot can bring a shared address like leads@ into the conversations inbox as a team email channel. When an email arrives from an address that is not already a contact, HubSpot creates a contact for it automatically.
That helps when the person emails you directly. With listing site notifications, the sender is the listing site, not the buyer. The buyer's details sit in the email body, and the inbox won't pull them into contact properties. That is the gap a parser fills.
Once the data is in HubSpot, workflows take over. HubSpot workflows can create a deal record, send an internal email notification, create a task, and (on Sales Hub or Service Hub Professional or Enterprise) rotate the record to an owner.
Where AI parsing helps
Template parsers break when the sender changes their layout. AI parsing reads the email more like a person would, so small changes are less likely to stop the flow. Two ways to use it:
- Use a parser with AI extraction built in, such as Parseur.
- Add an AI step to your automation. AI by Zapier has an "Analyze and Return Data" action that can pull details out of text and sort messages into categories, which is useful for working out which lead source an email came from.
AI still makes mistakes, so keep a check in place. A simple rule like "if the email field is empty, send it to a person to review" catches most problems.
How to set it up, step by step
- Create a forwarding address. Set up the parser mailbox or mailhook address. Then add a forwarding rule in your email so lead emails from each source go there automatically. Filter by sender address or subject line so only real leads are forwarded, not newsletters or receipts.
- Extract the fields. Send a few real sample emails from each source and define what to pull out: name, email, phone, company, the inquiry text and any listing or job reference. Build one template per source, because each source formats its emails differently.
- Match or create the contact. Search HubSpot by email address first. If the contact exists, update it. If not, create it. This is what stops a repeat inquiry from creating a second contact.
- Create the deal in the right pipeline. Create a deal, associate it with the contact, and put it in the correct pipeline and first stage. If different sources go to different teams, route them to different pipelines.
- Set the lead source. Write the source to a property on both the contact and the deal. Use a dropdown property with fixed values, so "Listing site A" is always spelled the same way and you can report on it.
- Notify the owner. Assign an owner and let them know straight away, with an internal email or a task that includes the inquiry text. Speed of reply matters more with emailed leads, because the buyer has often contacted several businesses at once.
- Handle duplicates and failures. Decide what happens when the same person inquires twice. You might add a note to the open deal rather than creating a new one. Also send any email the parser could not read to a person, so nothing is dropped without anyone knowing.
What to map
| Field in the email | HubSpot property |
|---|---|
| First and last name | Contact: First name, Last name |
| Email address | Contact: Email (used to match existing contacts) |
| Phone number | Contact: Phone number |
| Company name | Contact: Company name, or an associated company record |
| Inquiry or message text | A note on the deal, or a custom "Inquiry details" property |
| Listing, property or job reference | Deal: a custom reference property |
| Which site or provider sent it | Contact and deal: a custom "Lead source detail" dropdown |
| Date received | Deal: Create date (set automatically) |
Common mistakes
Duplicate contacts and deals
HubSpot deduplicates contacts by email address, but only if your flow searches first or uses a "create or update" step. Deals are not deduplicated automatically. If you don't check for an open deal before creating one, a buyer who inquires twice ends up with two deals and your numbers look better than they are. HubSpot lets you create unique value properties, so a listing or lead reference number can stop the same deal from being saved twice.
Missing or messy lead source
If the source isn't written to the record, you can't tell which listing site or provider is worth paying for. Set it in the flow itself, not by hand afterward.
Parsing breaks when the email layout changes
Lead providers change their email templates without warning. A template parser keeps running but fills fields with the wrong text, or leaves them blank. Check for empty required fields, send failures to a person, and review a few new records from each source now and then. AI parsing lowers this risk but does not remove it.
Paying for contacts you won't market to
HubSpot bills marketing contacts separately from non-marketing ones, and contacts created by an integration are non-marketing by default. Decide on purpose. If you plan to send parsed leads nurture emails, set them as marketing. If sales only calls them, leave them as non-marketing.
FAQ
Can HubSpot parse emails on its own?
Not in the way a parser does. The conversations inbox creates a contact from the sender's address, but it won't pull a buyer's details out of the email body. For that you need a parser or automation tool alongside HubSpot.
How do I automatically create a HubSpot deal from an email?
Forward the email to a parser or automation tool, extract the fields, find or create the contact by email address, then create a deal associated with that contact in the right pipeline. You can do this inside Zapier or Make, or create the contact there and let a HubSpot workflow create the deal.
Should I use Zapier or Make for email parsing?
Zapier's Email Parser is quick for one or two sources with a fixed layout. Make suits flows with more logic, such as several sources or different pipelines. If your emails are complex or change often, add a dedicated parser with AI extraction to either.
What happens if the same lead emails twice?
If your flow matches on email address, the existing contact is updated. Deals need their own check: look for an open deal first and add a note to it instead.
Will parsed leads count as marketing contacts in HubSpot?
By default, no. Contacts created through an integration or the API are non-marketing unless you change that setting or set the status in a workflow.
If leads still arrive in an inbox and get copied into HubSpot by hand, we can build the flow for you. See how we connect tools to HubSpot.