Create Lead

pipedrive.create_lead
ActionCRM & salesconnection required

Calls the Pipedrive API with the connection's credentials.

Create a lead in the Leads Inbox with POST /api/v1/leads. Pipedrive needs a title and either a person or an organization to attach it to.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Pipedrive
Secret shape
the Pipedrive API token, or {"api_token": "…"}
Config it needs
company_domain
Resolved by
config.connection_id, else node.connection_id

Configuration

10 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
title
Name of the lead.
stringYes———
owner_id
Id of the user who owns the record.
stringNo———
person_id
Id of the person the lead is for.
stringNo———
organization_id
Id of the organization the lead is for.
stringNo———
amount
Value of the lead. Sent with `currency` as Pipedrive's {amount, currency} object, so both are needed together.
numberNo—≥ 0—
currency
ISO 4217 currency code for `amount`, e.g. USD.
stringConditional—only with amount—
expected_close_date
When the lead is expected to close, as YYYY-MM-DD.
stringNo—matches \d{4}-\d{2}-\d{2}2026-01-31
was_seen
Whether someone has already opened the lead.
booleanNo———
fields
Any other Pipedrive body field, as a JSON object. Use this for anything the named fields above do not cover; the named fields win on a clash.
objectNo——{"visible_to":3}
custom_fields
Custom fields to write, as a JSON object keyed by the field's 40-character hash. Leads are a v1 resource, so these are sent as top-level keys rather than nested under custom_fields.
objectNo——{"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d":"Webinar"}
  • At least one of person_id, organization_id must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "custom_fields": {
    "1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d": "Webinar"
  },
  "expected_close_date": "2026-01-31",
  "fields": {
    "visible_to": 3
  }
}

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

Notes

  • This resource has no API v2 endpoint yet, so the call goes to /api/v1 and pages with start/next_start rather than a cursor.

See Create Lead run in a workflow.

In a technical demo we add the Pipedrive connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.