This article has expired. Please visit the OneCloud Knowledge Base for the latest documentation.


Premium BizApp

This BizApp provides functionality to interact with the data inside Salesforce, including loading, extracting and deleting data via SOQL and bulk operations. There are also functions for creating and managing Salesforce objects and updating and creating records.

For documentation on all available commands, see the Salesforce command reference.


Need a specialized command for Salesforce?

If there are specific operations that your company is looking to perform with Salesforce, please contact [email protected] to discuss the requirements and we would be happy to consider incorporating the capability into OneCloud.

Connection Setup

OneCloud connects to Salesforce via the REST API. The OneCloud Salesforce BizApp is compatible with all versions of Salesforce's Sales Cloud (Salesforce Essentials, Lightning Professional, Lightning Enterprise, and Lightning unlimited).

In order to automate functionality within your Salesforce from OneCloud, you'll need to navigate to the connection manager to create a connection.

From here, choose Salesforce from the service dropdown and select the appropriate Runner. Now, enter values for the following fields:



User Name

Salesforce user name


Salesforce password

Security Token

Salesforce security token. To obtain a security token, go to Settings -> My Personal Information -> Reset security token to have Salesforce email you a security token.


Salesforce instance - the characters before in your Salesforce URL (i.e. na73)


Security Token

Note that when you change the password to your Salesforce account, your security token will change and you will need to update it within OneCloud.

Connection Example

The following is an example of a working connection. Please substitute your own values.


In order for the OneCloud Salesforce connection to work properly, you will need to grant the selected user the proper permissions. The API Enabled permission is an absolute requirement, but from here, your Salesforce administrator may decide which objects can be accessed. Navigate to Administer -> Manage Users -> Profiles, select the relevant profile, and ensure that this permission is enabled.

At a minimum, objects must have "read" permission enabled in order for the OneCloud BizApp to perform the appropriate functions, and you may add more permissions at your discretion. For example, if you wanted to make bulk changes to Salesforce objects of a certain type, that object must have the "update" permission enabled. See below for an example of standard object permissions, and note that this also applies to any custom objects.


SOQL Queries

One of the easiest ways to extract data from Salesforce is by using SOQL. The syntax is very similar to SQL, and users can create a SOQL query in OneCloud to extract the results into a CSV.

OneCloud's SOQL Query command can extract large volumes of data, and it can be used to return data sets of 1 million or more records at a time. If a command fails because the SOQL query is incorrect or references objects that do not exist, OneCloud will notify users via the command's outputs.

Bulk Jobs

Users can take advantage of Bulk Jobs to insert, update, upsert, or delete records. Bulk jobs take a CSV as an input, and will return information on how many records were processed correctly.

If all records were processed correctly, the command will have completed successfully. Upon any records failing, OneCloud will return a CSV listing the row numbers of the failed records, along with the reason for the failure. Users can take advantage of OneCloud's branching logic to perform actions when the job fails, or simply upload the failures to Google Drive to be examined later.

Lastly, bulk jobs can be performed synchronously or asynchronously. When checking the "Wait for completion" checkbox, OneCloud will poll Salesforce and only move onto the next command once all records have been processed. In cases where you may not need the result of the job to perform the next action in your chain, users can leave "Wait for completion" blank. This will allow OneCloud to trigger the bulk job and immediately move onto the next action in the chain.


Salesforce to Anaplan

OneCloud makes it extremely simple to extract data from Salesforce and upload directly to Anaplan . Let's start by building a chain to facilitate that connection. Simply create a chain and add your first command. From the modal, select Salesforce -> SOQL Query.

Next, you'll need to fill out the parameters for this command. After naming it and selecting the appropriate connection, fill in your SOQL query. See the "Considerations" section above for more details on how to build your query (if you don't already have one). In addition, you can choose your Query Command. It will default to a standard query, but you may use Query All if you want to include deleted records.

Now, it's time to load the results of this SOQL query into Anaplan. Create a command below, and choose a Run Condition of "Success". This means that the command will only run if the previous command was successful. If the query were to fail, we wouldn't have data to upload.

From here, select Anaplan -> Upload File. Once you've named the command and selected a connection to your Anaplan account, fill out the form to include your Anaplan Workspace and Model. The Server File field determines what the file will be called in Anaplan.

Source file is where we want to use the results of our SOQL query, as it represents the data that will be uploaded to Anaplan. To select the results of the query, click on the < > icon to the right of Source file. You will see a left-hand menu open; scroll down until you see the Command section. Under the name of your command, click SOQL Query Output.

Finally, click Save. You now have a fully automated process to connect Salesforce to Anaplan. From here you may test this connection by running it via the Self Service page, or by scheduling it.

Updated 8 months ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.