Connect Pipedrive

Create a Pipedrive Person from an accepted HoneyFalcon lead through the Persons v2 endpoint.

Why it matters

The preset supplies a provider-ready Person mapping so sales teams can reduce manual contact entry while keeping account-specific authentication and custom-field keys under company control.

Where to work

Prepare the personal API token and a compatible custom Person field in Pipedrive. Then open Company -> Connectors, select New connector, choose Pipedrive contact, and select Load preset.

Steps

1. In the target Pipedrive account, obtain the personal API token for the integration owner and store it securely.
2. Create or identify a text custom field for Persons and copy its account-specific 40-character field key.
3. Load the Pipedrive contact preset in HoneyFalcon and keep the Persons v2 Destination URL with the write-only secret placeholder.
4. Replace REPLACE_WITH_DELIVERY_ID_PERSON_FIELD_KEY in the request template with the actual custom Person field key.
5. Review the name, emails, phones, selected fields, and Successful HTTP statuses 200 and 201.
6. Run Test draft with a unique synthetic identity, then Create connector or Save changes and Activate the saved revision.
7. Accept a new synthetic lead, inspect Delivery history, and confirm the resulting Person in Pipedrive.

See it in HoneyFalcon

Step 1 of 5: Pipedrive preset selected in the connector editor.

Step 2 of 5: Pipedrive destination and protected credential controls.

Step 3 of 5: Pipedrive payload fields and request template.

Step 4 of 5: Pipedrive request template and destination field mapping.

Step 5 of 5: Pipedrive endpoint and Successful HTTP statuses to review before creation.

Create the intended Pipedrive object

Prepare the account-specific values

The personal API token belongs to the target Pipedrive account and is entered as a write-only HoneyFalcon credential. The preset references it through the secret placeholder in the Destination URL.

Pipedrive custom fields use account-specific keys. Copy the actual Person field key rather than the display label visible in the Pipedrive UI.

Replace the placeholder before saving

The released template includes REPLACE_WITH_DELIVERY_ID_PERSON_FIELD_KEY as an explicit setup marker. Replace it with the custom Person field key if delivery_id should be stored in Pipedrive.

Keep delivery_id selected when the template references it. Do not leave the setup marker in an active connector.

Expect a Person, not a Lead Inbox item

The preset posts to /api/v2/persons and creates a Pipedrive Person with name, email, phone, and the configured custom field.

It does not create a Lead Inbox item. Pipedrive requires an existing Person or Organization relationship before a Lead can be created through that separate workflow.

Interpret the result correctly

The preset accepts HTTP 200 or 201 as legitimate successful responses. Delivered records that HTTP result.

Search for the synthetic Person in Pipedrive and confirm the identity fields and custom delivery field before rollout.

The Pipedrive connector is ready when

• The Destination URL uses /api/v2/persons and references the write-only credential without exposing the token.
• The request template contains the real custom Person field key and no setup marker.
• Successful HTTP statuses contains 200 and 201.
• A synthetic delivery creates a traceable HoneyFalcon result and the expected Person in Pipedrive.

Continue learning

• Start from: For operations - start here
• Related guide: Edit and test safely
• Previous: Connect HubSpot
• Next: Connect HighLevel