Salesforce

Connect Salesforce to your preprocessing pipeline, and use the Unstructured Ingest CLI or the Unstructured Ingest Python library to batch process all your documents and store structured outputs locally on your filesystem.

You will need:

The Salesforce prerequisites:

• A Salesforce account. Create an account.

• The Salesforce categories (objects) that you want to access, specified as a comma-separated list. Available categories include Account, Case, Campaign, EmailMessage, and Lead.

• The OAuth consumer key (client ID) and private key (PEM) for the Salesforce connected app. The PEM is a string that begins with —–BEGIN RSA PRIVATE KEY—– and ends with —–END RSA PRIVATE KEY—–. Create a connected app. Get the consumer key. Get the private key.

The Salesforce connector dependencies:

pip install "unstructured-ingest[salesforce]"

You might also need to install additional dependencies, depending on your needs. Learn more.

The following environment variables:

• SALESFORCE_USERNAME - The Salesforce username that has access to the required Salesforce categories, represented by --username (CLI) or username (Python).
• SALESFORCE_CONSUMER_KEY - The consumer key (client ID) for the Salesforce connected app, represented by --consumer-key (CLI) or consumer_key (Python).
• SALESFORCE_PRIVATE_KEY - The contents of the private key (PEM) associated with the consumer key for the Salesforce connected app, represented by --private-key (CLI) or private_key (Python), or
• SALESFORCE_PRIVATE_KEY_PATH - The local path to the (PEM) associated with the consumer key for the Salesforce connected app, represented by --private-key-path (CLI) or private_key_path (Python).

Now call the Unstructured Ingest CLI or the Unstructured Ingest Python library. The destination connector can be any of the ones supported. This example uses the local destination connector.

This example sends data to Unstructured API services for processing by default. To process data locally instead, see the instructions at the end of this page.

For the Unstructured Ingest CLI and the Unstructured Ingest Python library, you can use the --partition-by-api option (CLI) or partition_by_api (Python) parameter to specify where files are processed:

• To do local file processing, omit --partition-by-api (CLI) or partition_by_api (Python), or explicitly specify partition_by_api=False (Python).

  Local file processing does not use an Unstructured API key or API URL, so you can also omit the following, if they appear:

  • --api-key $UNSTRUCTURED_API_KEY (CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY") (Python)
  • --partition-endpoint $UNSTRUCTURED_API_URL (CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL") (Python)
  • The environment variables UNSTRUCTURED_API_KEY and UNSTRUCTURED_API_URL

• To send files to Unstructured API services for processing, specify --partition-by-api (CLI) or partition_by_api=True (Python).

  Unstructured API services also requires an Unstructured API key and API URL, by adding the following:

  • --api-key $UNSTRUCTURED_API_KEY (CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY") (Python)
  • --partition-endpoint $UNSTRUCTURED_API_URL (CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL") (Python)
  • The environment variables UNSTRUCTURED_API_KEY and UNSTRUCTURED_API_URL, representing your API key and API URL, respectively.

  Get an API key and API URL.