ActionPipedriveUpdated September 2026
How do I create a Pipedrive deal from a workflow?
Short answer: You can create deal in Pipedrive by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pipedrive Create Deal action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Deal Title title | string | Required | Deal Title. Example: Enterprise SaaS deal |
Deal Value value | string | Optional | Deal Value. Example: 15000 |
Currency currency | string | Optional | 3-letter currency code |
Person ID person_id | string | Optional | Pipedrive person (contact) ID to link |
Organization ID org_id | string | Optional | Organization ID. Example: 456 |
Pipeline Stage ID stage_id | string | Optional | Pipeline Stage ID. Example: 1 |
Expected Close Date expected_close_date | string | Optional | Expected 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 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 Deal support batch operations?
Run Create Deal 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
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.
ActionGet 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.
ActionGet 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.
ActionList 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.
ActionList Persons
Lists persons (contacts) from Pipedrive with filters for owner and update time. Used for CRM sync into your ESP or for cohort exports.
ActionUpdate Deal
Updates an existing Pipedrive deal: title, value, stage, status, expected close date, owner, or custom fields. Only the fields you pass are changed.