A common requirement is for any easy was to get PDFs, spreadsheets, Word docs or even paper (yes, real world) paper into Salesforce.  All of the files are relatively easy.  You can upload files as Content to a Library – but how do you get a piece of paper into Salesforce as Content?

  1. Scan document
  2. Save to computer
  3. Login to Salesforce
  4. Navigate to Content
  5. Upload file (this isn’t a great experience when using content, lots of nifty but slow AJAX)

So the point I am trying to make is this doesnt work great – imagine doing that for all documents sent to and received from your customer, all contracts etc. etc.

What I have is a way for you to skip steps 2,3,4 & 5.  Rather than scanning the document and creating a local file many scanners support directly emailing that attachment. So why not email it directly into Salesforce, and why not strip out meta data from the emails subject or body and add that information to the content record? Well this is Email2Content.  So, now we are getting that paper into Salesforce without even logging in – the same idea works for files.  All your doing is emailing a file to an email address.  So all those files you need to upload one by one can be attached to one email* and sent – easy peasy. *max file size of about 5MB, enough for most PDFs and general documents.

The really cool bit here is being able to populate fields using for example the subject.  In the example here we are using Email2Content to upload Id Documents into Salesforce and using the subject to tag the content.

Email2Content Mappings Tab

From the Email2Content Mapping tab you can configure all of your mappings…

Email2Content Mapping Tab

Email2Content Mapping record for ID Docs

To create an Email2Content Mapping you will first need to create your email service (this is in the develop menu of Setup but is very easy, no code at all).  Once you have your email service Salesforce will generate a long email address for you, this is what you see in the ‘Email2Content Email Service Address Field’.  Then all you need is a descriptive name and to provide a Library ID if you want to automatically associate the content with a Library.

Once you have created your mapping record your ready to go.  In the example below we have also cr

eated a field mapping record.  In this example we are reading the subject of the email into the CSVTag field – this is the field which shows the tags.  You could easily set a custom field based on subject or just as a static value – or what I recommend is adding an ‘Uploaded by’ field and populating this based on [From Email].

So this is Email2Content in a nutshell.  I am currently reading up on ISVforce docs and aim to get it listed very shortly in the AppExchange. Any questions or feature requests please leave a comment.

<span>%d</span> bloggers like this: