Get Deal: Pipedrive action

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 ID deal_id	string	Required	Deal ID. Example: 1

Sample request

{
  "deal_id": "e.g. 1"
}

Returns

{
  "data": {
    "id": 1,
    "title": "Enterprise Deal",
    "value": 15000,
    "stage_id": 3,
    "person_id": 123
  },
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Deal.

What does the Get Deal action do in Pipedrive?

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.

What inputs does Get Deal require?

Required: Deal ID. 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 Get Deal support batch operations?

Yes. Run Get 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