If you’re new to Unstructured, read this note first.
Before you can create a source connector, you must first sign in to your Unstructured account:
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.
After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.
You can also create source connectors with the Unstructured API. Learn how.
If you need help, reach out to the community on Slack, or contact us directly.
You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from Salesforce.
The requirements are as follows.
Your Salesforce username. To get this username, do the following:
The names of the Salesforce categories (objects) that you want to access, specified as a comma-separated list.
Available categories include Account
, Campaign
, Case
, EmailMessage
, and Lead
.
A Salesforce connected app in your Salesforce account.
If you do not already have a Salesforce connected app, to create one, start by creating or getting the certificate (.crt
) and private key (.pem
) files
that you will associate with the connected app.
If you do not have the certificate and private key files, you can use the openssl
utility on your local machine to create your own
private key and self-signed certificate, if your organization allows, by running the following commands, one command at a time:
Of course, you can change these preceding example filenames as needed. Be sure to store these generated files in a secure location.
To create a Salesforce connected app, do the following:
Log in to your Salesforce account.
In the top navigation bar, click the Quick Settings (gear) icon, and then click Open Advanced Setup.
In the Home tab, under Platform Tools, expand Apps, and then click App Manager.
Click New Connected App.
With Create a Connected App selected, click Continue.
At a minimum, fill in the following, and then click Save:
Connected App Name
API Name (can be the same as Connected App Name, but do not use spaces or punctuation)
Contact Email
Under API (Enable OAuth Settings), check Enable OAuth Settings.
For Callback URL, entering https://localhost
is okay if you won’t be using this connected app for other special authentication scenarios.
Check Use digital signatures, click Choose File, and browse to and select your certificate (.crt
) file.
For Selected OAuth Scopes, move the following entries from the Available OAuth Scopes list to the Selected OAuth Scopes list:
Uncheck Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows.
Leave Require Secret for Web Server Flow checked.
Leave Require Secret for Refresh Token Flow checked.
Check Enable Authorization Code and Credentials Flow.
On the connected app’s details page, click Manage, click Edit Policies, set the following under OAuth Policies, and then click Save:
The OAuth consumer key (client ID) for the Salesforce connected app.
To get the Salesforce connected app’s consumer key, do the following:
You must use your Salesforce account to do a one-time approval of the Salesforce connected app by using its consumer key and callback URL. To do this, while you are logged in to your
Salesforce account, browse to the following URL, replacing <client-id>
with the consumer key value. This URL assumes that the callback URL
is https://localhost
:
To ensure maximum compatibility across Unstructured service offerings, you should give the contents of the private key (.pem
) file to Unstructured as
a string that contains the contents of the file (not the private key file itself).
To print this string suitable for copying, you can run one of the following commands from your Terminal or Command Prompt.
In this command, replace <path-to-private-key-file>
with the path to the private key file.
For macOS or Linux:
For Windows:
To create the source connector:
Fill in the following fields:
Account
, Campaign
, Case
, EmailMessage
, and Lead
.If you’re new to Unstructured, read this note first.
Before you can create a source connector, you must first sign in to your Unstructured account:
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.
After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.
You can also create source connectors with the Unstructured API. Learn how.
If you need help, reach out to the community on Slack, or contact us directly.
You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from Salesforce.
The requirements are as follows.
Your Salesforce username. To get this username, do the following:
The names of the Salesforce categories (objects) that you want to access, specified as a comma-separated list.
Available categories include Account
, Campaign
, Case
, EmailMessage
, and Lead
.
A Salesforce connected app in your Salesforce account.
If you do not already have a Salesforce connected app, to create one, start by creating or getting the certificate (.crt
) and private key (.pem
) files
that you will associate with the connected app.
If you do not have the certificate and private key files, you can use the openssl
utility on your local machine to create your own
private key and self-signed certificate, if your organization allows, by running the following commands, one command at a time:
Of course, you can change these preceding example filenames as needed. Be sure to store these generated files in a secure location.
To create a Salesforce connected app, do the following:
Log in to your Salesforce account.
In the top navigation bar, click the Quick Settings (gear) icon, and then click Open Advanced Setup.
In the Home tab, under Platform Tools, expand Apps, and then click App Manager.
Click New Connected App.
With Create a Connected App selected, click Continue.
At a minimum, fill in the following, and then click Save:
Connected App Name
API Name (can be the same as Connected App Name, but do not use spaces or punctuation)
Contact Email
Under API (Enable OAuth Settings), check Enable OAuth Settings.
For Callback URL, entering https://localhost
is okay if you won’t be using this connected app for other special authentication scenarios.
Check Use digital signatures, click Choose File, and browse to and select your certificate (.crt
) file.
For Selected OAuth Scopes, move the following entries from the Available OAuth Scopes list to the Selected OAuth Scopes list:
Uncheck Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows.
Leave Require Secret for Web Server Flow checked.
Leave Require Secret for Refresh Token Flow checked.
Check Enable Authorization Code and Credentials Flow.
On the connected app’s details page, click Manage, click Edit Policies, set the following under OAuth Policies, and then click Save:
The OAuth consumer key (client ID) for the Salesforce connected app.
To get the Salesforce connected app’s consumer key, do the following:
You must use your Salesforce account to do a one-time approval of the Salesforce connected app by using its consumer key and callback URL. To do this, while you are logged in to your
Salesforce account, browse to the following URL, replacing <client-id>
with the consumer key value. This URL assumes that the callback URL
is https://localhost
:
To ensure maximum compatibility across Unstructured service offerings, you should give the contents of the private key (.pem
) file to Unstructured as
a string that contains the contents of the file (not the private key file itself).
To print this string suitable for copying, you can run one of the following commands from your Terminal or Command Prompt.
In this command, replace <path-to-private-key-file>
with the path to the private key file.
For macOS or Linux:
For Windows:
To create the source connector:
Fill in the following fields:
Account
, Campaign
, Case
, EmailMessage
, and Lead
.