You are viewing beta documentation for Formie 4.x.
CRM

Pardot

Connect Pardot to send enquiries to the records your team manages. You need access to configure the form in Craft and credentials for the destination account. The steps below establish the connection; finish by sending a test submission to verify the result.

Step 1. Create the Integration

  1. Navigate to Formie → Settings → CRM.
  2. Click the New Integration button.
  3. Select Pardot as the Integration Provider.

Step 2. Connect to the Pardot API

  1. Go to Pardot and login to your account.
  2. In the main menu, on the top-right, click the Settings icon and select Setup.
  3. In the left-hand sidebar, click on Apps → App Manager.
  4. Click the New Connected App button.
  5. Fill out all required fields.
  6. In the API (Enable OAuth Settings) section, tick the Enable OAuth Settings checkbox.
    • In the Callback URL field, enter the value from the Redirect URI field in Formie.
    • In the Selected OAuth Scopes field, select the following permissions from the list and click Add arrow button:
      • Manage Pardot services (pardot_api).
      • Perform requests on your behalf at any time (refresh_token, offline_access).
    • Untick Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows.
    • Tick Require Secret for Web Server Flow.
    • Untick Require Secret for Refresh Token Flow.
  7. Click the Save button.
  8. Copy the Consumer Key from Pardot and paste in the Consumer Key field in Formie.
  9. Copy the Consumer Secret from Pardot and paste in the Consumer Secret field in Formie.
  10. Click on the Manage button.
  11. Click on the Edit Policies button.
  12. In the OAuth policies section:
    • In the Permitted Users field, select All users may self-authorize.
    • In the IP Relaxation field, select Relaxed IP restrictions.
  13. Click the Save button.
  14. In the main menu, on the top-right, click the Settings icon and select Setup.
  15. Enter Business Unit in the Quick Find box, and click on Business Unit Setup.
  16. Copy the Business Unit ID from Pardot and paste in the Business Unit ID field in Formie.

Step 3. Test Connection

  1. Save this integration.
  2. Click on the Connect button in the right-hand sidebar.
  3. You‘ll be redirected to Pardot, where you must approve Formie to access your Pardot account.

Step 4. Form Setting

  1. Go to the form you want to enable this integration on.
  2. Click the Integrations tab.
  3. In the left-hand sidebar, select the name you gave the integration.
  4. Choose the data objects (record types) you want to use, and enable their mapping options where available.
  5. Map the required destination fields using the variable picker. Follow the requirements shown for each selected record type.
  6. Enable the integration.
  7. Click Save to save the form.

For a contact enquiry, map the visitor’s email and name where those fields are available.

Troubleshooting

Prospects Are Not Created, or Logs Show API v4 Errors

Formie uses the Pardot API v4 endpoints. If your account still uses the legacy Pardot Classic app (pi.pardot.com), Pardot returns an error such as Your account is unable to use version 4 of the API (error code 89).

Formie does not support the legacy Pardot Classic API. You will need an Account Engagement (Salesforce Pardot) business unit and OAuth connected app, as described above.

Check storage/logs/formie.log after a test submission for integration errors.

Verify a Submission

Save the form, open it on your site and submit recognisable test values. Find the test record in the selected CRM destination. Check the mapped values and whether the integration created a record or updated an existing one as intended.

If nothing arrives, check whether integration conditions matched, whether the submission was complete and non-spam, and whether Craft’s queue has processed the job. A successful connection check verifies credentials; it does not prove that field mapping and delivery work. See Connect and Test an Integration for a complete mapping and verification workflow.