Qudini has a native integration with Salesforce which allows for bi-directional data flow. It is possible to configure an integration to either pull data, push data or both. This can be configured to your usecase.
Setup and Authentication:
Note: You must have a Salesforce account with API access to use this integration. SFDC Editions with API Access include: Enterprise, Unlimited, Developer, and Performance. Any licenses that do not have this edition cannot communicate to external services via API.
During setup you will then be prompted to enter the credentials of the Salesforce user you will be authenticating with.
This user must be set up with the correct permissions in the Salesforce Admin UI, to ensure that you will be able to access all the available connector operations.
In order for Qudini to map to various object types we will first query the objects your Salesforce instance supports, then during the setup process we can configure which objects and fields to use. Please discuss your exact use-case with Qudini. We also always recommend first configuring against a Sandbox account for testing.
Common patterns:
Qudini -> Salesforce
A common approach is to push all appointments booked via Qudini into Salesforce so you have the data within your CRM.
Mapping Objects:
First you need to choose which object within Salesforce maps to the Qudini 'Customer' object. For some people this may be Lead or others may be Contact, or even another custom field.
Mapping Fields:
Once you have chosen your object, we then allow you to map the Qudini fields to the relevant Salesforce fields for that object.
The standard fields are:
| Field Name | Example |
|---|---|
Additional answers to questions can then also be mapped which are loaded from your Qudini account.
