# How to use a Righthand with Nimble

Prepare a Nimble deal review from an approved pipeline or CSV, retaining owners, privacy context, stages, and verified next steps.

By Righthand Team · 2026-10-09

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

## Start with a selected Nimble pipeline

Use Righthand with Nimble to prepare a deal-review brief for the owner of one pipeline. The useful result connects stage, ownership, and source notes to an explicit next-step question. It should not treat every related contact as a recipient or advance a deal because its description sounds promising.

Nimble's [deal feature guide](https://support.nimble.com/en/articles/6695934-nimble-s-deal-feature-overview) describes customizable pipelines, deal privacy, and CSV export. An owner-provided CSV is a concrete route when current native reads are uncertain. Keep its snapshot time and selected pipeline with the report.

## Define the fields and privacy boundary

Give the pipeline, included stages, owner mapping, and relevant custom fields. An illustrative partner-opportunity review might use Deal Name, Stage, Owner, Amount, Currency, Close date, and the team's next-action field. Use actual supplied labels and available record references.

Inspect Nimble's tools through [integrations](/integrations) before claiming live access or updates. If the needed native action is absent, use the approved export or a scoped browser review. The account's privacy settings and the report's destination should remain aligned.

## A complete example request

> At 11 AM America/Los_Angeles on Thursday, review the approved partner-pipeline CSV or authorized pipeline view. Prepare a private owner brief with deal reference, stage, owner, amount and currency, close date, supplied next action, and missing information. Retain related-contact roles only when explicitly provided. Do not change deals, create activities, or send messages. Deliver to me for pipeline-owner review. Reconcile the selected stages and deal count, and label export freshness and unavailable fields.

This example is illustrative. A probability value belongs to the recorded planning context; it does not independently establish whether the partner will accept an offer.

## Make the output easy to check

An example entry might say: “Partner pilot deal; stage Evaluation; owner present; close date missing; source note requests technical review; owner must confirm the next decision.” Keep the note reference and do not invent a meeting date.

A deal marked stuck under an account's stage-duration rules needs owner interpretation. It may be waiting on an agreed external event. The assistant can surface the recorded condition and ask a question without declaring the opportunity lost.

## Reconcile identities and historical snapshots

Use stable deal references when the export provides them. If it does not, return an ambiguity note and ask the owner for a reliable mapping before proposing updates. Duplicate names can identify distinct opportunities or markets.

A missing deal can reflect privacy, stage filtering, or a changed export. Do not infer deletion or completion from absence alone. For later approved native writes, retrieve the resulting state independently; for an export workflow, return a reviewed change worksheet for the owner to apply.

Define access through [Righthand connection permissions](https://docs.righthand.ai/guides/add-a-connection). Check [plans](/pricing) for recurring pipeline preparation and keep the pipeline owner responsible for customer commitments.