Instance · Pipelines
Pipeline Opportunities Introduction
Last updated 1 November 2026
Each deal in a pipeline: its stage, status, value, people and reasons, shown as cards on a board.
An opportunity is one deal you are working on, such as a quote to a new client. It sits in a stage of a pipeline and moves through the stages as the deal progresses, until it is won or lost. The board shows each opportunity as a card, so you see your whole pipeline at a glance.
Where to find opportunities
| Screen | What it shows |
|---|---|
| All Opportunities | Every opportunity in a table |
| Opportunity Board | Cards by stage, for one pipeline |
| Reports | All, open, won, lost and withdrawn opportunities |
Open an opportunity to see its details, related contacts, tasks, event stream and form submissions.
What an opportunity holds
| Field | Meaning |
|---|---|
| Name | What the deal is |
| Pipeline and stage | Where it is |
| Status | Open, won or lost. New opportunities start open |
| Value and probability | What it is worth, and how likely it is to close |
| Target conversion date | When you expect it to close |
| Contact, company and owner | Who it is with, and who on your team owns it |
| Won or lost reason | Why it ended. A pipeline can make the reason required |
From code
The Pipelines API manages opportunities at /pipeline/api/v2/opportunities. Custom-field values go in the same request. The module sends opportunity_created, opportunity_updated and opportunity_deleted webhooks.
Note
The docs instance has no opportunities, so none was read. The fields come from the Pipelines module reference in the Insites Logic Engine.
Common mistakes
- Sending the value as a number to the API. Value and probability are stored as text.
- Marking a deal lost without a reason on a pipeline that requires one. The form asks for it.
- Expecting a deleted company to still show on an opportunity. Archived companies are left out.