Lead email parser

Few businesses get all their leads through one form wired to the CRM. Real inquiries come from a contact form plugin that only sends an email, from directory listings and review sites, from partner and affiliate referrals, from trade show apps and from people who simply write to sales@. Each source formats the message its own way, and many bury the inquiry under marketing text, badges and unsubscribe links.

Speed matters with inbound leads, and copying details by hand is the slowest step. ParsedMail reads each email against one lead schema and ignores the footer, the signature and the reply history, so the CRM gets the inquiry itself. If you also handle inquiries that are really support requests, the support email parser uses the same mechanism.

Typed fields keep the CRM clean. The email type returns a valid address or null. The phone type normalizes numbers, so "(512) 555-0148" arrives in one consistent format. The money type turns "around 12k" into {"amount": 12000, "currency": "USD"}, and a date field turns "mid November" into a date with a lower confidence score, which tells you it was an interpretation. An enum field, for example lead_type with options such as new project, partnership and job inquiry, lets your automation route each lead to the right pipeline.

Values that are not in the email stay null. The parser uses only what the sender wrote, so it never invents a company name or a budget.

Every parsed email is posted as JSON to your webhook. Common setups:

• HubSpot. Zapier Catch Hook, then Find or Create Contact by email, then Create Deal with the service and budget.
• Salesforce. Make Custom webhook, then a Search Records step on Lead and Contact, then Create a Record on Lead with the lead source set from the parsed field.
• Pipedrive. n8n Webhook node, then the Pipedrive node to create a person, an organization and a lead.
• Your own CRM. Verify the ParsedMail-Signature header and insert the record directly.

Step-by-step setup is on the Zapier integration page and the Make integration page.

• Allowed senders. Limit the inbox to your form tool and directory notification addresses, for example @pro-directory.example. Other senders are logged as blocked_sender, not parsed and not counted.
• Duplicates. A notification resent with the same Message-ID, or the same sender, subject and body within 30 days, is marked duplicate.
• Classification. On Growth and Scale, give one inbox a lead schema and a schema for everything else, such as listing renewals or review alerts. Emails that fit neither go to the review queue.
• Low confidence. A lead with a missing required email address, or confidence under your threshold, waits in the review queue instead of creating a half-empty CRM record.

Plus tags let you tell sources apart without new inboxes. Give the directory [email protected] and your partners [email protected]. Both land in the same inbox and schema, and the to field of the result holds the address with its tag, so it shows which source sent the lead. When a source needs very different fields, create a separate inbox. Starter includes 5 inboxes, Growth 25 and Scale has no limit on inboxes.

Not every team runs a CRM. The same JSON can append a row to Google Sheets or Excel with one automation step, which is often how a lead process starts. The page on email to spreadsheet shows that setup. When you move to a CRM later, only the last step of the automation changes, the inbox and schema stay the same.