An Overview of Unito's Salesforce Integration

Unito syncs all Salesforce standard objects and custom objects to and from 50+ other apps and tools in our connector library.

What does this article cover?

What does Unito sync from Salesforce?
How do I connect Salesforce to Unito?
Necessary permissions in Salesforce
How do you sync Salesforce records with Unito?
Salesforce documentation references
Limitations and other considerations
Watch a demo of Unito's integration between Salesforce and Smartsheet

Each Unito flow can sync Salesforce records of one object type from across an entire organization to and from your other tools. You can also set up a flow that turns Salesforce records of one object type into records of another.

What does Unito sync from Salesforce?

Unito syncs Salesforce records — which can be from any type of standard or custom object — from your Salesforce organization to and from your other tools. You can also sync work items from other tools to Salesforce as new records of a single object type, automatically.

Here's a list of custom Salesforce field types supported by Unito.

Here's an example of a field mapping table in a flow:

Salesforce ServiceNow Fields New

Attachments

Unito can copy attachments to and from any Salesforce object, meaning the whole file will be available in any synced task as long as it's mapped to an attachment field in your other tool.

How to connect Salesforce to Unito

To securely connect your Salesforce account to Unito, simply click the "Connect" button on the Salesforce block within your Unito flow setup and follow the on-screen prompts to authorize Unito.

Connect Salesforce and Unito 1 (1)

Necessary permissions in Salesforce

To ensure Unito can sync your data smoothly, the Salesforce user account connected to Unito needs specific permissions:

Enable API Access:
The user profile must be API enabled. To enable this, go to Setup > Profiles > [Select User] > System/Admin Permissions and check the "API Enabled" box.
Object-Level Permissions:
The user should have the following permissions for each standard or custom object you want to sync.
1. Read
2. Create
3. Edit
4. Delete
5. View All
6. Modify All
Field-Level Security:
The user needs access to read, edit, and delete the specific fields you intend to sync.

To change the Owner ID field from another tool, the user must also have "Transfer Record" permissions and "Read" access to the new owner.

Additional Considerations:

Custom Objects: These permissions apply to both standard and custom Salesforce objects.
Minimal Access Principle: For security reasons, it's best practice to grant only the necessary permissions to the Unito user account.

How do you sync Salesforce records with Unito?

To connect Salesforce and/or another tool through Unito Sync Platform, users create flows. Flows represent the connection between Salesforce and other tools comprised of four steps:

You can read our generic guide to flow creation or one of these Salesforce-specific guides on how to sync:

How are actions, triggers, or rules configured in Unito?

You can create a rule in Unito through one of two ways:

With a choice field —like State, Urgency, and Category — filtering out certain options as necessary.
With any other field, filtering out records when that field is filled or empty. For example, you could filter out any records that don't have due dates filled in.

Salesforce documentation references

You can find more information about custom objects and fields from Salesforce's own documentation, including a list of all custom field types in SFDC.

This is an overview of the various primitive data types used in the Salesforce API, including their definitions, usage examples, and specific considerations within the Salesforce environment.
This is a list of additional field types supported by the Salesforce API.
And you can find a reference guide with key details about standard Salesforce objects here.

Limitations and other considerations

Closed Status records

We cannot create items with a Closed Status. For example, a Closed Won Opportunity or Closed Case. For this reason, you cannot:

Use a Closed Status as a rule
Sync historical records with a Closed Status

If you sync a record under a different status (for example, Prospecting) and then change this status to Closed, we will sync the change (for example in a status <> status mapping) and close out the sister task. This is the current behavior in the classic Salesforce connector.