Add Product To Deal
pipedrive.add_deal_product
ActionCRM & salesconnection required
Calls the Pipedrive API with the connection's credentials.
Attach a product line to a deal with POST /api/v2/deals/{id}/products. Pipedrive requires a product, a unit price and a quantity.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Pipedrive
- Secret shape
- the Pipedrive API token, or {"api_token": "…"}
- Config it needs
- company_domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
14 fields, 4 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
deal_id Pipedrive id of the deal to attach the product to. | string | Yes | — | — | — |
product_id Id of the product in the product catalogue. | string | Yes | — | — | — |
item_price Unit price for this line, in the deal's currency. | number | Yes | — | ≥ 0 | — |
quantity How many units of the product this line carries. | number | Yes | — | ≥ 0 | — |
tax Tax percentage or amount for this line. | number | No | — | ≥ 0 | — |
discount Discount for this line. | number | No | — | ≥ 0 | — |
discount_type Whether the discount is a percentage or a flat amount. | string | No | — | one of "percentage", "amount" | — |
tax_method How tax is applied to the line price. | string | No | — | one of "exclusive", "inclusive", "none" | — |
comments Free-text note stored on the line. | string | No | — | — | — |
product_variation_id Id of the product variation to attach instead of the base product. | string | No | — | — | — |
billing_frequency How often the line is billed for a recurring deal. | string | No | — | one of "one-time", "annually", "semi-annually", "quarterly", "monthly", "weekly" | — |
billing_frequency_cycles How many billing cycles the line runs for; Pipedrive allows up to 208. | number | No | — | 1–208 | — |
billing_start_date First billing date for a recurring line, as YYYY-MM-DD. | string | No | — | matches \d{4}-\d{2}-\d{2} | 2026-01-31 |
fields Any other Pipedrive body field, as a JSON object. Use this for anything the named fields above do not cover; the named fields win on a clash. | object | No | — | — | {"visible_to":3} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"billing_start_date": "2026-01-31",
"fields": {
"visible_to": 3
}
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Add Product To Deal run in a workflow.
In a technical demo we add the Pipedrive connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.