Email2Lead Pro for

Email2Lead Pro is an advanced email parser which parses an incoming email and creates a Lead by mapping email data to Lead. Mapping of email data is customizable. Extensive error and warning report enables administrator to tune the mapping easily.


  • Parse Email to Lead
  • Supports multiple email templates
  • Map specific text from Email to Lead Field
  • Configurable Option to attach lead to a campaign
  • Customizable Lead field value – from email or via config
  • Process Attachments
  • Out of box mapping of email attributes to Lead fields
  • Detailed Error Reporting
  • Process Unlimited Emails

AppExchange Listing:


Pricing is based on organization size (based on number of active standard users in your org), there is no limit on number of emails processed.

Organization Size (Business Size) Per Organization, Per Month Per Organization, Per Year
Small Business

(up to 5 Users*)



Regular Business

(Above 5, Below 100 Users)



Medium Size Business

(100 to 499 Users)




(500+ Users)

Email for Pricing along with standard user license count



Support is provided for initial setup via email on best effort basis. We also provide premier support plans. Kindly email your requirements to for pricing for support plans.

Please email your company name and production Org Id to after purchase.

Note: Once the payment is made, please allow 24 hours to reflect the licensing in your org.


Payment Options

Link to Admin guide: Email2LeadPro Admin Guide

Please let us know your comments or suggestions using below comment box.

Link to Admin guide (Older version 1.4.3): Email2Lead Admin Guide

Email2Lead Pro – Convert Emails to Leads (

22 thoughts on “Email2Lead Pro – Convert Emails to Leads (

  • January 26, 2018 at 8:56 pm

    Is there a way to create multiple criteria to parse emails containing similar information that have different structures? We have several web forms that come in for various reasons/campaigns, and the structure (depending on the source) of the email information is slightly different; which in turn makes the Starting and Ending Markers slightly different. Is there a way to handle this, or are we stuck with the single Start/End Marker?

    • March 17, 2018 at 8:16 am


      The latest version of Email2LeadPro can handle multiple email templates, you would need to setup an email addresses in Email Service for each email template (structure).

  • January 12, 2018 at 3:55 am


    Is the free version of email2lead still available.


    • March 17, 2018 at 11:50 am


      Unfortunately free version is no longer available however we do offer a free trial of 30 days.

      – CloudGofer

  • September 27, 2017 at 2:27 pm

    I recently installed this plugin and I’m getting an error like another person stated above:

    Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Parent]: [Parent]

    Is there something I’m doing wrong?

    Thank you

    • November 8, 2017 at 4:51 pm

      We are sorry for the inconvenience that you have faced, you can open a case regarding this issue at Our customer support team will help you to solve it.

  • September 20, 2017 at 3:06 pm

    I just installed this and followed the setup. When I tested sending to the Email2Lead Email adress I receive the following error:

    Error while processing Email2Lead:
    Argument cannot be null.

  • August 13, 2017 at 5:45 pm

    Kindly provide us with your contact details using Contact Us form, our professional services team will get in touch you to finalize the requirements and provide you a quote.

  • August 10, 2017 at 5:23 pm

    I am looking at this app for email to lead creation. We do need to assign the lead to a record type and owner upon creation from the email. I believe that using lead source would be adequate to fire a work flow for such assignment.
    We will be having about 100 leads per day max generated.
    How much will this cost us for the lead manager as a user and that volume of emails for conversion? This is for one of my clients who are very active in using web page generated emails to create leads. The leads are manually entered by the lead manager.
    Thank You!

  • May 9, 2017 at 2:41 pm

    Having trouble with Email2Lead. A little tricky to get going, but seems to be working except am having trouble with the Campaign ID.
    I have a mapping of
    Name = ‘Campaign’
    Token = ‘Hidden Campaign ID=”

    Submitted data is:
    Hidden Campaign ID=7011A00000169jdQAA

    I have confirmed that the campaign is valid. The configuration is the same as other fields which DO work. Is there an issue assigning to the campaign field?

    • May 10, 2017 at 5:17 am

      we will look into this and get back to you as soon as possible.

  • May 3, 2017 at 3:10 pm

    How does this work if the contact information isn’t directly included in the lead email? I’m assuming/hoping it pulls from the signature? If so, what if the signature is missing required fields?

    • May 10, 2017 at 5:21 am

      in the next version, we are adding new functionality which allow you to preset certain field values when email body is missing values. If you would like to be part of beta release , please let us know.

  • April 24, 2017 at 5:09 pm

    Hello Support Team,

    I am testing your application and it is working well.

    But I don’t know how to configure file attachment, I would like to keep file attachment to the lead.

    Is it possible ?



    • April 29, 2017 at 9:56 am

      Hello David,

      Unfortunately current version does not support configuring the file attachment, next version will support it, beta release next week.

      Thank you,
      CloudGofer Customer Success Team

  • April 17, 2017 at 7:28 pm

    I’m getting a strange error using Email2Lead:

    Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Parent]: [Parent]

    Our configuration is very simple: no field parsing, just capturing the body of the email as a Lead and using the defaults for Name, Company and so on based on the information in the email. This is in a Professional Edition org with the latest version of Email2Lead from the AppExchange. The error only occurs with some emails, but it repros consistently — 100% — with emails sent from a website “contact us” form. The complete error response is below. I submitted a case via Email2Lead support a week ago but never received any kind of response. Can someone please help?

    Error while processing Email2Lead:
    Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Parent]: [Parent]

    debug message: done with EmailProcessorHelper:processEmailBody

    before inserting the lead
    after upserting the lead
    creating note related record to the lead
    ———————————– Email Plain Text Body ————————————–
    Dear Staff,

    The customer has submitted a request for the ……

    Please find the details below:

    Requested ….
    Proposed Price : 100.00
    Username : a…t
    Phone : 907…0
    Email : a…t
    Message: contact me

    Please follow up with the customer for further process.

  • February 22, 2017 at 10:19 am


    I am testing your App and i didn’t succeed to create a lead. I followed every steps from your guide and it’s not working.
    When i send my email (to the email services =>email adresses) I have an error (that I can see in the developer console) : “Source from EmailToApexHandler could not be loaded”
    Can you help me on this ?

    I precise that I use a sandbox environment.

    Thank you.

  • February 19, 2017 at 2:05 am

    Thanks for your feedback. We have identified this as a bug in our app. We are in process of fixing the app.
    We are planning to submit new version of Email2Lead for security review next week, please drop us a note at support at, if you would like to have beta version for testing purposes.
    Thank you,
    CloudGofer Customer Success Team

  • February 17, 2017 at 8:30 pm

    I’ve been testing this app today. I followed your instructions. I enabled error message routing to my email address. However, on error, it does not send an email to this address, but instead an email to every user active or inactive in Salesforce. Any ideas?

      • February 24, 2017 at 10:32 pm

        I’ll update the package, but it may not be fixing the problem I had. In Salesforce settings at Email Service: Email2Lead / Failure Response Settings / Route Error Emails to This Email Address it’s implied that I can send to one specific email only. In your text for the patch though you you say: “Fixed Inactive admins selected for error/warning email message”. I don’t want the error messages to go to all active admins, just to the one email address specified in the email service definition.

        Wouldn’t it make more sense to send to all active admins or some such default only if Route Error Emails to This Email Address is left blank?

        • February 27, 2017 at 5:21 pm

          I used a workaround for this that is just a workaround, but seems to work. You just stright-clone the System Administrator profile and assign the clone profile to those you _don’t_ want to get error messages. Would still be better not to have to do this.


Leave a Reply

Your email address will not be published. Required fields are marked *