How to integrate Unify with Salesforce
To integrate Unify with Salesforce, authorize the Salesforce integration user in Unify, configure field mappings, and resume data sync. Enable writing separately when your workflow needs supported records sent back to Salesforce. Use CRM context to inform audiences, exclusions, and Plays.[1]
- Connection
- Native CRM sync
- CRM
- Tool
- Salesforce
- Unify
- Data flow
- Salesforce ↔ Unify
- Account-specific configuration
At a glance
- Connect the intended Salesforce integration user
- Configure readable fields before relying on CRM exclusions
- Enable writes separately and validate the supported object types
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
A promising signal needs context. The same company might be a new prospect, a current customer, or an account with an active deal. A useful workflow checks that relationship before it creates more work for a rep. After qualification, the CRM handoff should preserve the record identity and the fields the team already trusts.
A good fit when
Teams that manage customer and deal context in Salesforce and want that context to inform Unify audiences, exclusions, and Plays.
Reconsider the plan when
If the team has not agreed which fields identify customers or open opportunities, define those rules before designing the automation.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Account context | Choose the customer and opportunity fields that should change outreach eligibility. |
| Qualification | Test one protected account and one eligible prospect against the proposed exclusions. |
| CRM handoff | Choose Contacts and Accounts or Leads, and identify the supported fields that should return to Salesforce. |
| Review | Inspect the matched CRM record and confirm that populated fields and account ownership remain intentional. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Protect customer accounts
A rep is ready to launch outbound, but Salesforce holds the customer and open-opportunity context.
Start with the fields needed for exclusions. Record visibility matters before any write-back action.
- Identify the CRM fields that mean customer or active opportunity
- Map readable fields and confirm that the test records reach Unify
- Evaluate the exclusion on a customer and a non-customer before enabling the Play
Return a qualified prospect to the CRM
A prospect is ready for a sales handoff and the CRM should contain the supported record and activity.
Choose Contacts and Accounts or Leads before designing the handoff. Keep opportunity creation in Salesforce.
- Decide which person object fits the team’s CRM process
- Review matching fields, required values, and write permissions
- Run a controlled sync and inspect the destination record
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
The permitted Salesforce records appear in Unify, and an enabled sync action creates or updates the expected supported Salesforce record.
Check record identity, mapped fields, and the action result separately. A connected account or a resumed read sync does not establish that writes or email activity are working.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Salesforce.
Is the Unify Salesforce integration bidirectional?
Yes. Salesforce data can be read into Unify, and supported records can be written back when Enable writing to Salesforce is on. Read access, write settings, field mappings, and user permissions are separate controls.[1]
How often does Unify sync Salesforce?
Unify documents a read schedule of approximately 15 minutes. Large batches of changed records can take longer, and field-mapping changes trigger background reprocessing. This is not a real-time delivery guarantee.[3]
Does Unify overwrite Salesforce fields?
For existing records, Unify fills empty fields and preserves populated fields unless they are Unify-specific fields. New records use the fields enabled for writing and applicable defaults. Check the mapping and user permissions for the exact destination field.[3]
Can Unify create Salesforce opportunities?
No. Salesforce opportunities are read into Unify for context, filters, and exclusions. Unify does not create or update those opportunity records.[3]
Can I connect a Salesforce sandbox?
The setup guide asks you to contact Unify support first so a dedicated testing login can be created. Complete that step before using the regular connection instructions for a sandbox.[1]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Read timing is approximate and depends on the volume of changes
- The integration does not deduplicate pre-existing Salesforce records
- Sandbox access and account-specific permissions need to be checked with the relevant admins
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Salesforce workflow.
Read sync + enabled writes
| Decision | What to know |
|---|---|
| Read schedule | Approximately every 15 minutes; larger changes can delay completion[3] |
| Person matching | Email address for Contacts and Leads[3] |
| Company matching | Normalized website domain for Accounts[3] |
| Existing values | Empty fields can be filled; populated fields are preserved except Unify-specific fields[3] |
| Opportunities | Read into Unify for context and exclusions; Unify does not create or update them[3] |
| Field permissions | Mappings and integration-user permissions determine accessible and writable fields[2] |
Map the fields your team actually uses for ownership, customer status, and exclusions. A populated CRM field is not a general overwrite target. Use documented default values when a required destination field has no mapped value.
Technical setup reference
References and requirements for the Salesforce connection.
Connection requirements and setup checklist
Before connecting
- A Salesforce subscription with API access and an integration user
- A Salesforce admin who can assign the required permissions
- A decision on creating Contacts and Accounts or Leads; contact Unify support before connecting a sandbox
Choose and authorize the integration user
Choose a dedicated integration user where possible. In Unify, open Settings → Integrations → Salesforce, select Connect, and authorize the intended Salesforce user.[1]
Resolve permission requirements
Review the Permissions widget in Unify. Check API access and the documented object permissions with your Salesforce admin. Enable Enhanced Email if you want Unify to write email messages.[2]
Resume reads and enable intended writes
Select Resume to start reading Salesforce data. Turn on Enable writing to Salesforce when your mappings and workflow are ready for writes.[1]
Validate a controlled record
Compare a record you control across both systems. Then run the intended sync action and inspect its Salesforce record and activity. This is a suggested validation, not a completed test.[3]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
Connection cannot be authorized
Ask your Salesforce admin to check that the Unify Connected App is installed and unblocked in Connected Apps OAuth Usage.[1]
An exclusion cannot see a customer
Check that the integration user can read the records and fields used by the exclusion. Restricted data cannot be used by Unify to evaluate that rule.[2]
A changed mapping is not reflected yet
Mapping changes trigger background reprocessing. Allow that work and the normal read sync to complete before treating the result as a failed mapping.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
