Pardot
Step 1: Create an API user in Pardot
To connect Pardot with Plecto, you'll need to provide an email, password and a user key.
We recommend you to create a separate API user for using Plecto. This way, your password and possibility to use API won't be removed once you enable Salesforce User Sync.
-
In Pardot, go to Admin > User Management > Users.
-
Click Add User.
-
Give the user a name such as API Plecto.
-
Add an email that's not used in Salesforce or Pardot.
If your company can use emails with +something parameter such as mike+apiuser@example.com, you can use this nifty trick to create an API user. The email address appears to be original, but in reality all emails will be sent to mike@example.com.
-
Give the user an Administrator role.
-
(Optional) Check or uncheck your email preferences.
-
Click Create user.
-
Ignore the prompt to create a CRM Username – it should be left blank (No CRM username set).
-
Check your email and open the activation link to set a password for your new API user.
You have now created a new API user that you're going to use for Plecto. You can find all the necessary credentials under Admin > User Management > Users.
Step 2: Integrate Pardot with Plecto
-
In Plecto, go to Data sources > New data source > Pardot.
-
(Optional) Rename your credentials.
-
Enter the API credentials you created in Step 1.
-
Email: Add the email of the API user you created in Step 1.
-
Password: Enter the password you created for the API user.
-
User key: Enter the API User Key.
-
Choose the time zone that matches the time zone set in your Pardot account.
-
-
Click Next.
-
Select the data you want to import.
-
Configure your data source settings. Here, you can change the title, choose the default date, select which fields to import, and more.
-
Click Next to choose how much data to import and how long you want to keep it in the data source.
-
Click Import to finish.
Available data
Currently, you can import the following data from your Pardot account to Plecto:
Update frequency: 1h
Supports custom fields? No
Supports webhooks? No
Supports automatic registration deletion? No
Supports relations? No
Update frequency: 2m
Default member field: assigned_to
Default date field: created_at
Supports custom fields? No
Supports webhooks? No
Supports automatic registration deletion? No
Supports relations? No
Update frequency: 2m
Default member field: assigned_to
Default date field: created_at
Supports custom fields? Yes
Supports webhooks? No
Supports automatic registration deletion? No
Supports relations? No
Update frequency: 2m
Default member field: assigned_to
Default date field: created_at
Supports custom fields? No
Supports webhooks? No
Supports automatic registration deletion? No
Supports relations? No