The Salesforce integration transfers customers, contacts, and opportunities from Salesforce to ZEP. Salesforce is the leading system for all imported records.
Data direction: Salesforce → ZEP
Product line availability
Note: The Salesforce interface is included in ZEP Track, ZEP Control, ZEP Operations, and ZEP Business. No additional booking is required. In ZEP Clock it does not appear in the Interface Marketplace, because only the HR interfaces are offered there.
Setup and configuration are reserved for administrators.
Prerequisites
To set up the integration, you need:
Salesforce credentials for one of the two login methods. For OAuth 2.0 (recommended) these are My Domain URL (OAuth), Consumer Key (OAuth), and Consumer Secret (OAuth), for the Legacy Login (Token) username, password, and security token. The choice between the two methods appears only while legacy credentials are still stored. If you set the integration up anew, or once the move to OAuth is complete, ZEP shows the OAuth fields only
Administrator access in ZEP
Access to Administration > Interfaces > Interface Marketplace
Warning: Salesforce is gradually restricting the login with username, password, and security token. From the Salesforce release Winter ’27 the Salesforce user in use additionally needs the permission Use Any API Authentication, and with Summer ’27 Salesforce switches this login method off entirely. These are Salesforce release names and not calendar years, so the dates fall earlier than the figure suggests. Move existing connections to OAuth 2.0 in good time, otherwise the synchronisation stops.
Setting up the integration
In ZEP, go to Administration > Interfaces > Interface Marketplace and choose the login method.
For OAuth 2.0 (recommended) you enter three values:
My Domain URL (OAuth): the address of your Salesforce org in the form https://company.my.salesforce.com. You find it in Salesforce under Setup > My Domain.
Consumer Key (OAuth) and Consumer Secret (OAuth): both come from the External Client App you create for ZEP in Salesforce.
In Salesforce this app must have the Client Credentials Flow enabled and a user stored that it runs as. If either is missing, Salesforce rejects the login and ZEP names exactly these two points in the error message.
For the expiring Legacy Login (Token) you enter the following instead:
Username: Your Salesforce username
Password: Your Salesforce password
Token: The security token from your Salesforce profile security settings
Save the settings. You can then start the import.
Optional import scope restriction
You can control which Salesforce Accounts are transferred to ZEP: create a custom field named "ZEP" in Salesforce. Only accounts where this field is deactivated (value false) are excluded from the import. If the field is activated or empty, the account is imported.
Salesforce automatically creates the API name ZEP__c when the field is added – this name must not be changed.
Data transfer
The Salesforce interface transfers several data objects between the two systems.
Accounts as customers
ZEP imports the following fields from Salesforce Accounts into ZEP customer master data:
Salesforce (Accounts) | ZEP (Customer data) |
Account Number | Customer No. |
IsDeleted | active/inactive |
Account Name | Name |
Street (Billing Address), State | Address lines |
Postal Code (Billing Address) | Postal code |
City (Billing Address) | City |
Country (Billing Address) | Country |
Phone | Phone |
Fax | Fax |
Website | WWW |
Description | Remark |
Note: Salesforce is the leading system. Imported customer data cannot be changed in ZEP while the connection to Salesforce is active. The delivery address is also synchronized. The standard address is set as the billing address.
Contacts as customer contacts
Salesforce contacts are imported as customer contacts in ZEP. The table below shows which Salesforce field is transferred into which ZEP field. Fields that Salesforce names differently from ZEP are listed as well, so you can follow the mapping:
Salesforce (Contacts) | ZEP (Customer contacts) |
Salutation | Form of address, derived from the values Mr., Ms. and Mrs. |
First Name | First name |
Last Name | Name |
Title | Job title |
Phone | Phone |
Fax | Fax |
Mobile Phone | Mobile |
Description | Remark |
Opportunities as projects
Salesforce Opportunities can be automatically created as projects in ZEP. Configure which Opportunity stages should trigger project creation in the integration settings.
The following Salesforce stages are available:
Prospecting
Qualification
Needs Analysis
Value Proposition
Id. Decision Makers
Perception Analysis
Proposal/Price Quote
Negotiation/Review
Closed Won
Closed Lost
Select the stages at which ZEP should automatically create a new project. When an Opportunity reaches one of the selected stages in Salesforce, ZEP creates the corresponding project on the next import.
Set up synchronization
Set up synchronization in ZEP under Administration > System > Tasks. Create a new task Salesforce import to run the import automatically at regular intervals.
The Customer import setting controls what the next import run transfers:
Full import: Transfers all records from Salesforce. Only this option is available for the first import.
Only changes since the last successful run: Transfers only records changed since the last complete import. Available only after a first complete import.
You can trigger the import manually at any time: under Administration > System > Tasks via the Start Task Now action. Salesforce is the leading system for all imported data. Make changes directly in Salesforce.
To remove the Salesforce connection for a customer, click Remove marking as Salesforce customer in the customer master data. The connection can be restored at any time via Import from Salesforce customers.