getting Started

Overview

The Pepper Cloud CRM source is used to synchronize CRM Lead, Contact, and Opportunities to TTO CDP. The mapping relationship is shown in the table below:

potential

Contact Person

Opportunity (Open)

A deal was reached

Lost opportunities

Pepper CRM

Lead

Contact

Opportunity (OPEN)

Opportunity (WON)

Opportunity (LOST)

TTO CDP

Contact

QualifiedLead

RequestQuote

ConvertedLead

UnconvertedLead

parameter

Parameter name

must

describe

API Key

yes

Pepper's private application key is the API key.

Admin ID

Yes (post-configuration)

Administrator ID; instructions for filling it in are provided below.

Cdp ID Name

yes

The field name you created in Pepper CRM to set the CDP ID.

Eno Code Name

yes

The field name you created in Pepper CRM to set the ENO code.

Custom Field Maps

Yes (post-configuration)

Pepper allows you to customize the encrypted field key mapping string; the filling method is given below.

CRM Configuration

CRM Custom Fields

  1. Enter the Customization section and click Custom fields.

  1. Create cdp_id and eno_id fields

Create fields in Lead.

The above is an example of cdp_id . The process is the same for eno_id , and it will look like this after creation:

  1. In the Customization System fields, create a `Weber Form` option for the source.

Click "Create new", enter "Weber Form", and save.

  1. Go to the Field mapping in Customization and set the field mapping.

Configure webhook workflow

Four types of workflows need to be created:

Reference URL: https://sg.fn.topkee.com/source-626680188572674936/automation?api_key=xxxxxxx Note the settings for the Method, Headers, and Body partitions.

cdp - lead created:

cdp - contact created:

cdp - opportunity created

cdp - opportunity updated

Note the HTTP request in the Integration category.

Configuration source

  1. Enter Integration to obtain the API Key

Click Create new

Select all permissions for private applications

Done → Save. Click to enter the created private application.

Copy the API key and configure it in the source settings.

  1. Fill in the previously set cdp_id and eno_id into the two required fields below.

  1. Save the source configuration, then reopen the source configuration by clicking the source link above to open a new page.

The opened webpage contains two lines of data, separated by commas. One line contains the Custom Field Maps configuration, and the other line contains the Admin ID configuration. Copy and paste the data into the webpage, then save.

  1. Once configured, the source can be tested.