How to create person in Pipedrive

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Full Name name	string	Required	Full Name. Example: John Doe
Email email	string	Optional	Email. e.g. "john@example.com"
Phone phone	string	Optional	Phone. e.g. "+15551234567"
Organization ID org_id	string	Optional	Link to an existing organization

Sample request

{
  "name": "e.g. John Doe",
  "email": "john@example.com",
  "phone": "+15551234567",
  "org_id": "e.g. 456"
}

Returns

{
  "data": {
    "id": 123,
    "name": "John Doe",
    "email": [
      {
        "value": "john@example.com"
      }
    ]
  },
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Person.

What does the Create Person action do in Pipedrive?

Creates a new person (contact) in Pipedrive with name, email, phone, organization, owner, and any custom fields. Used to push inbound leads into the CRM.

What inputs does Create Person require?

Required: Full Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Pipedrive returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Person support batch operations?

Yes. Run Create Person inside a Loop node to process arrays. TinyCommand handles Pipedrive's rate limits automatically so you don't have to throttle manually.

More actions