ActionPipedriveUpdated June 2026

How do I create a Pipedrive deal from a workflow?

Short answer: Drop the "PipedriveCreate Deal" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Deal Title
title
stringRequiredDeal Title. Example: Enterprise SaaS deal
Deal Value
value
stringOptionalDeal Value. Example: 15000
Currency
currency
stringOptional3-letter currency code
Person ID
person_id
stringOptionalPipedrive person (contact) ID to link
Organization ID
org_id
stringOptionalOrganization ID. Example: 456
Pipeline Stage ID
stage_id
stringOptionalPipeline Stage ID. Example: 1
Expected Close Date
expected_close_date
stringOptionalExpected Close Date. e.g. "YYYY-MM-DD"
Sample request
{
"title": "e.g. Enterprise SaaS deal",
"value": "e.g. 15000",
"currency": "USD",
"person_id": "e.g. 123",
"org_id": "e.g. 456"
}
Returns
{
"data": {
"id": 1,
"title": "Enterprise SaaS deal",
"value": 15000,
"currency": "USD",
"stage_id": 1
},
"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 Deal.

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

FAQ

Questions about Create Deal.

What does the Create Deal action do in Pipedrive?
Creates a new deal in the Pipedrive sales pipeline with title, value, currency, person, organization, stage, expected close date, and owner. The entry point for converting qualified leads into pipeline.
What inputs does Create Deal require?
Required: Deal Title. 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 Deal support batch operations?
Yes. Run Create Deal inside a Loop node to process arrays. Tiny Command handles Pipedrive's rate limits automatically so you don't have to throttle manually.
More actions

Other Pipedrive actions.

Action
Create Person
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.
Action
Get Deal
Retrieves a Pipedrive deal by ID with title, value, stage, person, organization, owner, and custom fields. The standard read after a trigger fires with an ID.
Action
Get Person
Returns a Pipedrive person by ID with their emails, phones, organization, owner, and custom fields. Used to enrich trigger payloads or render contact UI.
Action
List Deals
Lists deals from Pipedrive with filters for owner, stage, status (open/won/lost), and update time. Used for pipeline reports, forecasting, and warehouse exports.
Action
List Persons
Lists persons (contacts) from Pipedrive with filters for owner and update time. Used for CRM sync into your ESP or for cohort exports.
Action
Update Deal
Updates an existing Pipedrive deal: title, value, stage, status, expected close date, owner, or custom fields. Only the fields you pass are changed.

Send create deal from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.