Create Person
pipedrive.create_person
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Create a person with POST /api/v2/persons. Pipedrive needs a name; an email or phone is sent as its primary entry.
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
9 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
name Full display name of the person. | string | Yes | — | — | — |
first_name Given name; Pipedrive builds `name` from it. | string | No | — | — | — |
last_name Family name; Pipedrive builds `name` from it. | string | No | — | — | — |
email Primary email address. Sent as Pipedrive's emails array with primary set; use `fields` to write several addresses. | string | No | — | email format | — |
phone Primary phone number. Sent as Pipedrive's phones array with primary set; use `fields` to write several numbers. | string | No | — | — | — |
org_id Id of the organization the person belongs to. | string | No | — | — | — |
owner_id Id of the user who owns the record. | string | No | — | — | — |
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. | object | No | — | — | {"visible_to":3} |
custom_fields Custom fields to write, as a JSON object keyed by the field's 40-character hash. Read the hashes with the matching Pipedrive: List * Fields node. | object | No | — | — | {"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d":"Enterprise"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"custom_fields": {
"1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d": "Enterprise"
},
"fields": {
"visible_to": 3
}
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- A custom field is addressed by its 40-character hash, never by its display name. Read the hashes with the matching Pipedrive: List * Fields node.
See Create Person 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.