Short answer: Drop the "Pipedrive → Create Deal" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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" |
{"title": "e.g. Enterprise SaaS deal","value": "e.g. 15000","currency": "USD","person_id": "e.g. 123","org_id": "e.g. 456"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.