Pipedrive action

Get Deal Details (Pipedrive)

Retrieve the details of a specific deal by its ID from Pipedrive using API v2.

Pipedrive logoPipedrive
pipedrive-get-deal-details
crmReturns in secondsLight tier
Input

What it needs.

Map each field to a column in your table. Optional fields can stay empty.

FieldType
  • id
    The ID of the deal you want to retrieve.
    number

When to use this.

The "Get Deal Details (Pipedrive)" action allows users to retrieve comprehensive information about a specific deal by its unique ID from the Pipedrive CRM platform using API v2. The primary input parameter is the deal ID (number), which identifies the deal to be fetched. Upon execution, the action returns a variety of output fields, including success status (boolean), deal title (text), deal value (number), currency (text), and key identifiers such as person ID, organization ID, and pipeline ID. Additional details include status, probability, expected close date, and various activity counts, providing a holistic view of the deal's lifecycle. This action is particularly useful for sales teams and CRM administrators looking to analyze deal performance, track progress, and manage customer relationships effectively within the CRM category.

Output

What it returns.

Every field this action writes back to the row. Click a line to expand nested objects.

FieldType
  • success
    Success
    nullableboolean
  • id_out
    Id Out
    number
  • title
    Title
    text
  • creator_user_id
    Creator User Id
    nullablenumber
  • value
    Value
    number
  • currency
    Currency
    text
  • person_id
    Person Id
    number
  • org_id
    Org Id
    number
  • pipeline_id
    Pipeline Id
    number
  • stage_id
    Stage Id
    number
  • owner_id
    Owner Id
    nullablenumber
  • status
    Status
    text
  • probability
    Probability
    nullablenumber
  • lost_reason
    Lost Reason
    nullabletext
  • visible_to
    Visible To
    nullablenumber
  • expected_close_date
    Expected Close Date
    text
  • add_time
    Add Time
    nullabletext
  • update_time
    Update Time
    nullabletext
  • close_time
    Close Time
    nullabletext
  • won_time
    Won Time
    nullabletext
  • first_won_time
    First Won Time
    nullabletext
  • lost_time
    Lost Time
    nullabletext
  • stage_change_time
    Stage Change Time
    nullabletext
  • is_deleted
    Is Deleted
    nullableboolean
  • is_archived
    Is Archived
    nullableboolean
  • origin
    Origin
    nullabletext
  • source_lead_id
    Source Lead Id
    nullabletext
  • next_activity_id
    Next Activity Id
    nullablenumber
  • last_activity_id
    Last Activity Id
    nullablenumber
  • product_count
    Product Count
    nullablenumber
  • file_count
    File Count
    nullablenumber
  • note_count
    Note Count
    nullablenumber
  • follower_count
    Follower Count
    nullablenumber
  • email_message_count
    Email Message Count
    nullablenumber
  • activity_count
    Activity Count
    nullablenumber
  • done_activity_count
    Done Activity Count
    nullablenumber
  • undone_activity_count
    Undone Activity Count
    nullablenumber
  • participant_count
    Participant Count
    nullablenumber
  • last_incoming_mail_time
    Last Incoming Mail Time
    nullabletext
  • last_outgoing_mail_time
    Last Outgoing Mail Time
    nullabletext
  • smart_bcc_email
    Smart Bcc Email
    nullabletext
  • local_won_date
    Local Won Date
    nullabletext
  • local_lost_date
    Local Lost Date
    nullabletext
  • local_close_date
    Local Close Date
    nullabletext
  • label_id_output
    Label Id Output
    nullablearray
  • custom_field_out
    Custom Field Out
    nullableobject
  • origin_id
    Origin Id
    nullablenumber
  • channel_output
    Channel Output
    nullablenumber
  • channel_id_output
    Channel Id Output
    nullabletext
  • acv
    Acv
    nullablenumber
  • arr
    Arr
    nullablenumber
  • mrr
    Mrr
    nullablenumber
  • archive_time_output
    Archive Time Output
    nullabletext
Workflow

How this fits a workflow.

Trigger → Get Deal Details (Pipedrive) → enrich → push to your CRM. You set it up once; after that it runs without you.

  1. Step 1TriggerNew row, form submit, or schedule.
  2. Step 2Get Deal Details (Pipedrive)The Pipedrive action runs.
  3. Step 3EnrichWaterfall fills missing fields.
  4. Step 4Push to CRMHubSpot / Pipedrive / Zoho CRM / GoHighLevel.

Two actions you can chain after this one:

Get Deal Details (Pipedrive)Get Deals by Person (Pipedrive)Delete Lead (Pipedrive)
Reliability

Throughput & reliability.

How fast it drains a table, and what happens when the upstream provider has a bad day.

  • Per-minute limitNo public cap
  • Per-day limitPlan-defined
  • RetriesAutomatic w/ backoff
  • Failed lookupsZero credits

Who runs this

GTM EngineerRevOpsAgency

Light tier. See pricing; per-action credit cost is private.

FAQ.

Mostly. Fast actions fill the cell in a few seconds. Long-running ones run in the background and write back to the row when they finish, so you can close the tab.

No. A failed lookup costs zero credits. When a provider misses or times out, the waterfall moves to the next one and you only pay for the match you actually got.

No. Run it on one cell, on a selection, on the whole table, or on a schedule. Same action either way.

HubSpot, Pipedrive, Zoho, and GoHighLevel are bidirectional, with Salesforce coming soon. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Get Deal Details (Pipedrive) in 60 seconds.

Connect the account, drop the action on a column, run it on your rows.