Answers.Body: <p>This would require an extension to do.</p>
  <p>That said, I'm not sure this is the best approach for your use case.</p>
  <p>If you have a form on your website, it seems like it would be better to integrate that form directly with CiviCRM instead of using inbound email processing.  For VolunteerMatch, I would use their <a href="https://solutions.volunteermatch.org/open-network-api" rel="nofollow noreferrer">API</a> with <a href="https://lab.civicrm.org/extensions/form-processor" rel="nofollow noreferrer">Form Processor</a> to process the message rather than inbound email processing.</p>
  <p>That second item is a complex solution if you're new to CiviCRM, but within the reach of a non-coder, as opposed to writing an extension.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-06-20T20:46:48.657Z
Answers.LastActivityDate: 2022-06-20T20:46:48.657Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>Is there a way to have CiviCRM create contacts from email addresses found in the body of an inbound email?  We have a number of different sources that send us emails with addresses in the email bodies that we want to capture (for example, we receive volunteer applications from a form on our website, and also from VolunteerMatch - both contain the applicant's email address in the email body).  However, it looks like inbound email processing only parses email headers by default.  Is there something obvious we're missing?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-06-20T20:11:04.543Z
Comments.Text: you are not missing anything obvious imo
Comments.UserDisplayName: petednz - fuzion
Tags: <email>
Title: Create Contacts From Inbound Email Body?
ThreadText: # Create Contacts From Inbound Email Body?
  
  (Asked by: username_0 on 2022-06-20)
  
  Is there a way to have CiviCRM create contacts from email addresses found in the body of an inbound email? We have a number of different sources that send us emails with addresses in the email bodies that we want to capture (for example, we receive volunteer applications from a form on our website, and also from VolunteerMatch - both contain the applicant's email address in the email body). However, it looks like inbound email processing only parses email headers by default. Is there something obvious we're missing?
  
  **Tags:** email
  
  > **Comments:**
  > **username_1**: you are not missing anything obvious imo  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2022-06-20. Score: 2
  
  This would require an extension to do.
  
  That said, I'm not sure this is the best approach for your use case.
  
  If you have a form on your website, it seems like it would be better to integrate that form directly with CiviCRM instead of using inbound email processing. For VolunteerMatch, I would use their [API](https://solutions.volunteermatch.org/open-network-api) with [Form Processor](https://lab.civicrm.org/extensions/form-processor) to process the message rather than inbound email processing.
  
  That second item is a complex solution if you're new to CiviCRM, but within the reach of a non-coder, as opposed to writing an extension.
  
  
  ---
  
  