Pipedrive CRM integration: sync form leads to Persons
Connect Pipedrive to Panther Hook with OAuth, map your form fields, and automatically create or update Persons from approved submissions.
What Pipedrive integration does
Panther Hook sends eligible, approved production submissions from a selected form to Pipedrive CRM as Persons. It searches for an exact matching email first, then updates an existing Person or creates a new one. This uses the same native integration delivery pipeline and retry history as other destinations.
This integration does not automatically create Deals, Leads, or Organizations. Empty or missing source fields do not overwrite existing contact details. If multiple Pipedrive Persons already have the same email, delivery stops with an error rather than guessing which Person to update.
The integration requires a Pipedrive OAuth app and an available provider connection in your environment. If Pipedrive is shown as temporarily unavailable, contact support or check its release status before enabling the destination.
Connect Pipedrive and choose a form
Open your formsStep 1: Open native integrations
Sign in to Panther Hook and select the intended workspace. Go to Forms, open the form that receives your leads, and select Integrations. Choose Pipedrive CRM from the provider list.
Step 2: Authorize via Pipedrive OAuth
Choose Connect Pipedrive. Finish the authorization in the Pipedrive browser window and return to Panther Hook. A workspace Owner or Admin must authorize this connection. Access tokens and refresh tokens are stored securely by Panther Hook and are never entered into a form field or given to an AI assistant.
Each CRM connection is scoped to one workspace. To use a different Pipedrive account, disconnect the previous connection first; this also disables associated destinations so pending deliveries cannot be silently redirected.
Step 3: Set up Person field mapping
Choose a destination name and map your source fields to Pipedrive Person properties. Email is required for matching. Name and phone are optional. The field selector can show supported writable custom Person fields when the OAuth connection is available.
Save the destination and enable it when your workspace plan has an available integration slot. Destinations belong to a selected form; connecting Pipedrive does not automatically send leads from every form.
Step 4: Verify a delivery
Use Test connection to verify that Panther Hook can reach the authorized Pipedrive account. This does not create a Person. To verify actual sync, submit a synthetic approved production-mode lead and check that a Person with the test email was created in your Pipedrive test account.
Repeat with the same email and a changed nonempty name: the existing Person should be updated. Check Integration delivery log or Open full delivery history for provider errors and retry attempts. Remove only your synthetic test Person afterward.
Pipedrive field mapping example
This is an example of Panther Hook mapping configuration, not a Pipedrive API request. Map email to a field that contains a valid email address. Optional name and phone values can come from other form fields.
Pipedrive custom Person properties use provider-specific field codes. Only map to writable fields returned by your connected account. Read-only or unsupported complex field types must not be sent as arbitrary strings.
Dashboard test submissions are marked as tests and do not enter production native integration delivery. A synthetic approved production-mode submission is needed to confirm the full end-to-end CRM path.
{
"email": "fields.email",
"name": "fields.name",
"phone": "fields.phone"
}Troubleshooting and billing
- If Connect is unavailable, make sure Pipedrive is enabled for your environment, you have Owner or Admin permissions, and an OAuth app has been configured.
- If synchronization does not run, confirm that the destination is enabled, the submission was approved, and your plan allows the destination and delivery attempts.
- If a Person is missing, inspect the integration delivery attempts. Expired OAuth access tokens are refreshed automatically; provider rate limits and temporary failures can be retried by the existing queue.
- If duplicates already exist in Pipedrive with the same email, resolve them in Pipedrive before retrying. The integration does not select an arbitrary duplicate.
- Disconnecting Pipedrive disables that workspace’s related destinations and prevents further pending deliveries through the disconnected connection.
- Panther Hook uses the existing native integration allowances, not a separate CRM synchronization quota. Any Pipedrive subscription or app access fees are governed by Pipedrive.
Official Pipedrive API reference
Pipedrive’s developer documentation covers OAuth authorization, Persons, PersonFields, API v2 requests and API usage limits. Panther Hook exposes only the supported Person synchronization features described above.
Pipedrive developers