Email to Lead Salesforce: Create Salesforce Leads From Inbound Email With Every Field Filled
Turn the lead notification emails your team retypes into Salesforce leads, with name, company, phone and source already in the right fields
Lead marketplaces, partner referrals, website form notifications and trade show follow ups all arrive as email, and Salesforce has no built-in way to read them. MailParse connects to the mailbox they land in over IMAP, pulls the fields you name out of the body and any HTML table, and exports one clean row per lead as CSV, Excel or JSON, mapped to Salesforce Lead fields.
Connect a Gmail or IMAP mailbox to parse new mail automatically, or paste an email below to test the converter now.
Create a free account to download. No credit card required.
Salesforce does not ship an Email-to-Lead feature. Web-to-Lead only accepts form posts, and Email-to-Case creates cases, not leads. To turn inbound lead emails into Salesforce leads you build an Apex email service, chain Email-to-Case into a Flow, license an AppExchange app, or parse the mailbox first. MailParse takes the last route: it reads each lead email, pulls first name, last name, company, email, phone and lead source into their own columns, and gives you a CSV the Data Import Wizard turns into leads.
- No Apex
- Name the fields instead of coding a handler
- Last Name + Company
- The two fields Salesforce requires, split out
- CSV / JSON
- Ready for the Data Import Wizard
- Any IMAP inbox
- Gmail, Outlook.com, Microsoft 365, or your host
Search the Salesforce IdeaExchange and you will find a long-standing request titled "Introduce a Standard Email-to-Lead Functionality". It exists because the feature does not. Salesforce gives you Web-to-Lead, which creates a lead when a web form posts to it, and Email-to-Case, which turns an email into a case. Neither one reads a lead notification email and creates a lead from it. So the leads that arrive by email, a quote request forwarded by a partner, a marketplace notification, a "new submission" email from a WordPress or Webflow form, a list of booth visitors from a trade show app, sit in a shared inbox until someone on the sales team copies them in by hand.
Copying them in by hand is where the money leaks. Speed to lead matters, and a lead that waits in an inbox until Monday is a lead a competitor already called. Retyping also drops data: the phone number goes into Description, the company is misspelled, the lead source is left blank, so the report that should tell you which vendor sends the best leads cannot be built. The fix is to treat those emails as data. Each one carries the same handful of values every time, and those values map one for one onto Salesforce Lead fields.
MailParse is the parsing step. You connect the mailbox the lead emails land in, name the fields you want (first name, last name, company, email, phone, lead source, product interest, budget, or any custom field), and MailParse reads them out of each message, including emails that carry the details in an HTML table. You get one row per lead, and the CSV loads straight into Salesforce through the Data Import Wizard or Data Loader, where your lead assignment rules can route each record to the right rep. This page compares that route honestly with the Apex, Flow and AppExchange options, including when one of those is the better fit.
What you get instead of retyping lead emails
The parts of Email-to-Lead that Salesforce leaves for you to build.
Every lead field in its own column
Name the values once, such as first_name, last_name, company, email, phone and lead_source, and MailParse returns each as a separate column. The phone number stops living in Description and starts being a field a rep can click to call.
Last Name and Company split out correctly
Salesforce will not save a lead without Last Name and Company. MailParse separates a full name into first and last and pulls the company name from wherever the sender puts it, so imports do not fail on the two required fields.
Works across lead sources with different layouts
A marketplace, a partner and your own website form each format the same lead differently. Because extraction keys off the field name rather than a fixed position, one setup reads all of them without a separate rule per sender.
Reads leads sent as an HTML table
Many form tools and lead vendors send the submission as a two-column HTML table of labels and values. MailParse reads the table as data, where a Flow formula on the flattened text body usually cannot tell where one value ends and the next begins.
Clears the backlog already in the inbox
Connect the mailbox and the lead emails already sitting there can be parsed too, not only new ones. That turns months of unlogged inquiries into leads you can still follow up, which a trigger that fires on new mail never does.
CSV for Salesforce, Excel for everyone else
Download a CSV shaped for the Data Import Wizard or Data Loader, a formatted Excel workbook for a sales manager who wants to review the list first, or JSON for a developer who is scripting the insert.
How to create Salesforce leads from email with MailParse
Four steps from a shared lead inbox to assigned Salesforce leads.
Connect the lead inbox
Connect the mailbox your lead emails arrive in over IMAP, such as leads@ or sales@. Senders change nothing, and you can also drop in a single saved .eml or .msg lead email to test.
Name the Lead fields
List the values you want using names that match your Salesforce fields: FirstName, LastName, Company, Email, Phone, LeadSource, plus any custom fields your team reports on.
Check your three hardest emails
Run the forwarded chain, the vendor that sends an HTML table and the form that puts the company inside a sentence. Adjust a field name if a column comes back empty.
Import and assign
Download the CSV and load it with the Data Import Wizard, ticking your lead assignment rule so each record lands with the right rep, or hand the file to Data Loader on a schedule.
Who needs Email-to-Lead in Salesforce
US sales teams whose best leads arrive as email rather than through a form Salesforce can see.
Home services and contractors
Lead marketplaces and directories send each new job request as an email notification. Parse the customer name, phone, ZIP code and job type into leads before the competitor who got the same notification calls first.
B2B sales with partner referrals
Resellers, distributors and referral partners email you introductions in their own format. Capture the contact, company and deal notes as a lead with the partner recorded as the lead source, so partner performance shows up in reports.
Marketing ops running third-party forms
Webflow, WordPress, Typeform and landing page tools that are not wired to Web-to-Lead still send a notification email for every submission. Turn those notifications into leads without rebuilding every form.
Event and trade show teams
Badge scan apps and event platforms often email the attendee list after the show. Parse the rows of that table into one lead per visitor, with the event recorded as the source, instead of pasting a spreadsheet by hand.
MailParse vs building Email-to-Lead inside Salesforce
No code to own
An Apex email service is a class with test coverage and a deployment for every sender change. MailParse is a list of field names you edit in a form.
Real fields, not Description
The Email-to-Case plus Flow workaround usually copies the subject into Last Name and the body into Description. MailParse fills each Lead field with its own value.
Where native wins
If every lead comes from one sender in a fixed plain text layout and your security review requires everything inside the org, an Apex email service keeps data in Salesforce and costs only developer time.
Old mail counts
Triggers only see new messages. MailParse reads the mailbox archive, so inquiries that were never logged can still become leads.
Four ways to get Email-to-Lead in Salesforce, compared
Salesforce leaves Email-to-Lead to you, and each route trades setup effort against how well the lead fields get filled. Here is an honest side by side. If the same inbox also takes support mail, the Salesforce Email-to-Case parser covers the case side, and four ways to fill case fields from Email-to-Case goes deeper on Flow and Apex.
| Decision point | MailParse, then import | Apex email service | Email-to-Case plus Flow | AppExchange email-to-lead app |
|---|---|---|---|---|
| Who builds it | The sales or ops owner, from a form | A Salesforce developer, with test classes | An admin comfortable with Flow | An admin, after procurement and security review |
| How lead fields get filled | Each named value lands in its own column | Whatever the code parses out of the body | Usually subject to Last Name, body to Description | Depends on the app, often rules per sender |
| Lead email sent as an HTML table | Read as a table, values kept apart | Only if you parse the HTML yourself | Flattened to text before the Flow sees it | Varies by app |
| When a sender changes layout | Named fields keep matching | Code change and redeploy | Formula returns blank, silently | Rule edit for that sender |
| Emails already in the inbox | Yes, the mailbox archive is readable | No, only mail sent to the service address | No, only new cases | Rarely |
| Data stays inside Salesforce | No, parsed outside and imported | Yes | Yes | Yes, for native apps |
| Good fit when | Several lead sources, tables, or a backlog to recover | One steady sender and developer time to spare | A handful of leads and only name plus notes needed | Policy requires a native, supported package |
Apex email services, Email-to-Case and Flow are included with Salesforce editions that support them, so their cost is developer or admin time. AppExchange apps are licensed separately by their vendors. Salesforce features change between releases, so confirm current behavior in your org before you build. No pricing is implied here.
Frequently asked questions
Does Salesforce have email to lead?
No. Salesforce has Web-to-Lead for web forms and Email-to-Case for support email, but no standard Email-to-Lead feature, which is why a request for one sits on the IdeaExchange. Teams fill the gap with an Apex email service, an Email-to-Case plus Flow workaround, an AppExchange app, or by parsing lead emails and importing them as leads.
How do I create a lead from an email in Salesforce?
For a single email, open the Salesforce extension in Outlook or Gmail and create the lead from the message. For a steady stream, parse the lead emails into fields first: connect the mailbox to MailParse, name FirstName, LastName, Company, Email and Phone, then load the CSV with the Data Import Wizard to create one lead per email.
Can Email-to-Case create leads instead of cases?
Not directly. Email-to-Case always creates a case. A common workaround routes lead mail to its own Email-to-Case address, then a record-triggered Flow creates a lead from the new case and deletes it. It works for low volume, but the Flow only has the subject and body text, so most lead fields stay empty.
How do I automatically create leads from emails in Salesforce?
Automation needs something to read each email and split it into fields. Inside Salesforce that is an Apex class implementing Messaging.InboundEmailHandler behind an email service address. Outside it, a parser such as MailParse reads the mailbox and produces lead rows you import on a schedule with Data Loader, without code to maintain.
What is the Web-to-Lead limit in Salesforce?
Salesforce accepts up to 500 Web-to-Lead submissions in a 24-hour period. Submissions over the limit are not created as leads right away and are handled through a pending queue and notification to the default lead creator. The Data Import Wizard, by contrast, loads up to 50,000 leads per import, which suits batches of parsed email.
Which fields are required to create a lead in Salesforce?
Last Name and Company are required on the standard Lead object, and your org may add more through validation rules or required custom fields. Lead emails often put the full name on one line and the company inside a sentence, so splitting those two values reliably is what keeps an import from failing.
Can Einstein Activity Capture create leads from emails?
No. Einstein Activity Capture syncs emails and events and associates them with existing leads, contacts and opportunities so they show on the activity timeline. It does not read a lead notification email and create a new lead record with its fields filled. You still need a parsing step for that.
Can MailParse read lead details inside an attached PDF?
MailParse reads the email body and HTML tables and records the filename of any attachment, but it does not read the contents of a PDF or spreadsheet attachment. Most lead notifications put the details in the body. When a vendor sends leads only as an attached file, extract that file with a document tool first.
Stop retyping lead emails into Salesforce
Connect the inbox your leads arrive in, name the Lead fields you need, and download a CSV the Data Import Wizard turns into assigned Salesforce leads.