This guide is intended for Salesforce administrators and outlines the exact permissions, object access, and field-level visibility needed for setting up the Clozd Salesforce integration.
Use this documentation to create a dedicated API-only integration user that enables secure and scoped read-only access to Salesforce data required by Clozd.
Overview
Clozd’s Salesforce integration is primarily read-only and accesses data via the Salesforce API. We recommend creating a dedicated integration user in Salesforce with only the necessary permissions for improved data security and traceability.
This integration user does not need to be associated with a real person or hold a full Salesforce license. A standard API-access-enabled user with the correct scoped permissions is sufficient.
Step 1: Create the Integration User
- Go to Setup > Users > New User
- Fill out required fields (e.g., First Name: Clozd, Last Name: Integration, Email: clozd.integration@yourdomain.com)
- Assign:
- A Profile with API access (e.g., “API Only”, “Integration User”, or a custom profile that includes API access)
- Active status
- Optionally, set Password Never Expires for long-term automation
Step 2: Assign Object Permissions
Grant the integration user read-only access to the following standard Salesforce objects:
- Opportunity
- Account
- Contact
- OpportunityContactRole
- User
If product-level data is included in your integration, you may also need:
- Product
- OpportunityLineItem
- Pricebook2
- PricebookEntry
If your org uses custom objects or custom fields to store required data, be sure to extend read access accordingly.
Tip: You can grant access through a custom Profile or via Permission Sets, depending on your Salesforce org structure.
Step 3: Grant Field-Level Access
The table below lists recommended and required fields Clozd may query as part of the integration. However, field mapping is fully controlled by your team—you decide which fields Clozd should access during the implementation process.
Important: While it’s possible to grant access on a field-by-field basis, we recommend granting the integration user read-only access to entire objects instead. This reduces future overhead when additional fields are added, as it avoids the need to contact a Salesforce admin each time a new mapping is needed.
Recommended Fields
| Clozd Field | Salesforce Object | Salesforce Field Name |
|---|---|---|
| Organization Name | Account | Account Name |
| Outcome | Opportunity | Won |
| Closed Date | Opportunity | Close Date |
| Created Date | Opportunity | Created Date |
| Organization Domain | Account | Website |
| Participant Email | Contact | |
| Participant First Name | Contact | First Name |
| Participant Last Name | Contact | Last Name |
| Participant is Primary | OpportunityContactRole | Primary |
| Participant Role | OpportunityContactRole | Role |
| Sales Rep Email | User | |
| Sales Rep Name | User | Full Name |
Additional Fields (Optional but Helpful)
| Clozd Field | Likely Salesforce Object |
|---|---|
| Amount | Opportunity |
| Region | (Custom or Account) |
| Outcome Type | (Custom or Opportunity) |
| Opportunity Name | Opportunity |
| Currency | Opportunity |
| Headcount | (Custom or Account) |
| Industry | Account |
| Lead Source | Opportunity |
| Revenue | (Custom) |
| Segment | (Custom or Account) |
| Product | OpportunityLineItem |
| Participant Phone | Contact |
| Participant Title | Contact |
| Opportunity ID | Opportunity |
| Outcome | Opportunity |
| Stage | Opportunity |
Tip: If you're unsure where a field lives (e.g., it may be custom), Clozd can assist with field mapping and verification during onboarding.
Connected App Usage Restrictions
It's possible you get the following error. If this is the case, you will need to enable one of the following permissions on your integration user:
- “Use Any API Client” permission — If API Access Control is enabled, this is the only permission that gives access to use uninstalled apps.
- “Approve Uninstalled Connected Apps” permission — If API Access Control isn’t enabled, trusted users can use uninstalled apps with this permission. (Added in Summer ’25, it allows trusted users to self-authorize and use uninstalled connected apps.)
For more information on this update, here is a Salesforce article that dives deeper into the issue: Prepare for Connected App Usage Restrictions Change
Optional: Enabling Two-Way Integration (Push Link to Salesforce)
By default, Clozd only pulls data from Salesforce. However, there's an optional feature that allows Clozd to push a link to a published interview back to Salesforce.
Once enabled, Clozd will populate a designated URL field on the Opportunity record with a link to the published Clozd interview.
Requirements
- The field must be on the Opportunity object
- The field must be of type URL
To Enable
- In the Clozd Platform, navigate to the Configuration tab.
- Click on the Integrations tab.
- Under Salesforce, click Settings.
- Toggle on Push Link to Salesforce.
- Select the Salesforce URL field (click “Refresh” if newly created).
- Click Save.
Tip: If needed, create a custom field in Salesforce such as “Clozd Interview Link” with a URL data type.
Optional: IP Whitelisting
IP whitelisting means we tell Salesforce to trust login requests for this Integration User only if they come from specific, approved internet locations—such as our company servers or a secure cloud environment. If a login attempt comes from anywhere else, Salesforce blocks it.
This adds an extra layer of protection by limiting where sign-ins can originate. Even if someone were to get the username and password, they still wouldn’t be able to log in unless they were connecting from one of our approved, secure systems.
Here is an approved list of IP Addresses:
34.207.18.60
44.221.101.122
3.208.50.63
34.236.17.252
4.38.208.146
208.185.41.218Note: IP addresses may change periodically.
Need Help?
If you have questions or need assistance validating access, contact your Clozd Program Manager or support team by emailing support@clozd.com. We're happy to help verify field mappings and confirm setup.
Comments
Article is closed for comments.