Salesforce Technical Overview

Partner Fleet offers two distinct options for implementing the Salesforce Integration: a standard out-of-the-box integration and a middleware third-party software solution. This document aims to provide a comprehensive overview of the use cases for each option and to address frequently asked questions, ensuring you have all the information needed for a successful integration.

When to use the native Partner Fleet integration?

Use Partner Fleet when:

The process is standard without custom conditionals.
There are no unique fields or back-and-forth requirements.
The only field needed back from Salesforce is the ID.

When to use Middleware?

Use Middle when:

There are custom conditionals, such as only sending accounts if users have reached a specific role.
There’s a need to send over additional information like custom fields or records other than leads, accounts, contacts, and users.
There are custom objects in Salesforce that need to be connected to our system.

What can be pushed from Partner Fleet (PF) to Salesforce (SFDC) with the native Partner Fleet integration?

Accounts
Contacts (Users in Partner Fleet)
Leads

What can be pulled from Salesforce (SFDC) to Partner Fleet (PF) with the native Partner Fleet integration?

The current integration does not pull data from SFDC into PF. Any historical data needed from SFDC would have to be manually imported. Only the IDs from SFDC will be pulled into Partner Fleet.

Which record types can be created?

Partner Fleet Integration (PF) to Salesforce (SFDC): Accounts, Contacts/Users, Leads
Middleware: Can handle custom objects and additional record types, provided they represent the three standard objects (account, contact, lead).

What is the deduplication process?

Current Process: Basic deduplication checks for website and email domain. If they exist, the existing record is used. If they don’t exist, a new record is created.
Enhancements: Planned improvements include allowing selection of stages for leads, vendors, and contacts.

Can we use trigger events to determine when a record is created in SFDC?

Yes, records in SFDC can be created based on trigger events, such as approving a submitted lead in Partner Fleet. This is available through the native Salesforce Integration and Middleware.

Which forms can trigger a data sync with Salesforce?

Any form can trigger a webhook to Salesforce through Zapier or Middleware.

Request a Partner form when there’s an integration request submitted
Partner Applications that when approved will create an account that syncs over to SFDC.
Lead Forms on the public Marketplace
Lead Reg submission by partner in the Partner Portal

Can historical data in SFDC from the previous marketplace platform be ingested into Partner Fleet and populate dashboards accurately (chronologically)?

Currently historical data is not being pulled into Partner Fleet. Manual upload would be required for historical data to populate dashboards accurately.

Can a change in Stage/Status in SFDC update the Stage/Status on the lead in Partner Fleet?

The feature to pull in stage or status from SFDC to PF is not yet implemented. This enhancement is planned for future updates.