Pipedrive

Choose Create Pipedrive Lead or Deal under Actions → Marketing & CRM. Enter the company subdomain from company.pipedrive.com and an API token. The token is sent in the x-api-token header, never in URLs.

Map the email and name fields. An optional company field matches an organization by its exact name. Email matching is exact and case-insensitive. More than one matching person or organization stops the action so an arbitrary record is not selected.

Choose Lead or Deal and a title. Deals can use pipeline and stage IDs; the selected stage must belong to the selected pipeline. A value can be zero. Specify a three-letter currency when supplying a value. Optional follow-up subject, activity type, and due date create a linked activity.

Custom field maps are JSON objects whose keys are Pipedrive's 40-character field API keys. Configure separate maps for person, organization, and lead/deal. Exact [FIELD] tokens preserve the submitted type; use JSON literals for fixed numbers, booleans, arrays, or null. Pipedrive validates each destination field type. Existing people retain their email list; explicitly mapped name, phone, organization, and custom fields are updated. Omitted optional values are left alone.

Persons, organizations, deals, stages, pipelines, and activities use API v2. Leads use API v1 with its different organization/value/custom-field format. The action result records person, organization, opportunity, and optional activity IDs.

Each completed operation is checkpointed. A retry of a failed activity does not recreate the recorded lead/deal. Pipedrive does not offer the same send idempotency contract as Resend: an ambiguous timeout after a remote create may still require checking the provider for duplicates before manual replay. Simultaneous submissions for the same new contact can also race the initial search.

References: authentication, Persons, Deals, Leads.