ActionPipedriveUpdated September 2026

How do I create a Pipedrive person (contact)?

Short answer: You can create person in Pipedrive by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pipedrive Create Person action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Person in Pipedrive — start free All 7 Pipedrive actions

Create Person in Pipedrive — start free

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.

Triggered by

Apps that pair well as the trigger for Create Person.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Pipedrive

2 Google Sheets triggers

HubSpot → Pipedrive

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Pipedrive returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Person support batch operations?

Run Create Person inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Pipedrive's rate limits.

More actions