# How to use a Righthand with Pipedrive

Review Pipedrive deals using pipeline and stage IDs, expected close dates, owner context, and a reconciled follow-up worksheet.

By Righthand Team · 2026-10-09

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-pipedrive

## Prepare a follow-up review from one pipeline

Righthand can help review Pipedrive deals that need an explicit next-step decision. The useful output is a worksheet for the sales owner, with deal identity and source evidence. A pipeline summary should not convert an expected close date into a promise or treat a stage as proof of a completed customer action.

Pipedrive's [deals reference](https://developers.pipedrive.com/docs/api/v1/Deals) describes deal identity, pipeline and stage filters, expected_close_date, and related values. Keep those fields separate from the business's interpretation of the stage. The account's configuration determines what each stage means.

## Give filters and ownership rules explicitly

Provide the pipeline, included stages or approved saved filter, time interval, and owner mapping. For an illustrative renewal review, select open renewal deals and the activities or notes that the owner permits the assistant to inspect.

Check the actual Pipedrive tools through [integrations](/integrations). If deal or activity reads are unavailable, provide an approved export or authorize a browser review. A provider endpoint that updates a deal does not prove that a native Righthand write action is exposed or authorized.

## A worked first-run request

> At 2 PM America/Los_Angeles on Tuesday, review open deals in the approved renewal pipeline under the supplied filter. Return a private worksheet with deal ID and link, stage ID and mapped label, owner, expected close date, value with currency, and accessible next-step evidence. Flag missing or conflicting information. Do not modify deals, schedule activities, or email contacts. Send to me for sales-owner review. Reconcile the filters, retrieved pages, and unique deal count.

This example is illustrative. The report should describe an unavailable activity source as unknown, not conclude that no follow-up exists.

## Make the worksheet actionable

An example entry could say: “Renewal opportunity; expected close date next week; owner present; latest supplied note requests a pricing review; next action needs owner confirmation.” The assistant should not supply a discount or make a new commercial commitment.

If two deals share an organization, retain both identities. They may represent distinct contracts, products, or periods. An apparent duplicate belongs in a review group rather than being merged automatically.

## Reconcile dates and stage changes

On repeat runs, compare the same deal IDs and report changed dates or stages within their existing worksheet entries. Refresh the mapping when a pipeline is reconfigured. Do not silently substitute a similarly named stage from a different pipeline.

Exports, pagination, and account permissions can limit completeness. Keep the source snapshot and missing coverage visible. If the owner approves supported changes, apply only the specified fields and reread their values afterward. A successful request is not sufficient evidence that the expected next step was recorded correctly.

Define authority through [Righthand's connection guide](https://docs.righthand.ai/guides/add-a-connection). Check [pricing](/pricing) for recurring pipeline preparation, and leave the customer relationship and commercial decisions with the named sales owner.