Instance · Pipelines
Pipelines Introduction
Last updated 1 November 2026
The stages your deals move through, with display settings, targets and webhooks per pipeline.
A pipeline is the series of stages your deals pass through, from first contact to won or lost. You can have several, for example one for new business and one for renewals. Each pipeline has its own stages, display settings, custom fields, sales target and webhooks.
Where to find pipelines
In the admin, open Pipelines and choose Configuration. Adding or editing a pipeline has four tabs:
| Tab | What you set |
|---|---|
| Details | Name, status, sales target and whether a won or lost reason is required |
| Stages | The stages in order, with their colors and the message shown when a stage is empty |
| Display Fields | Which fields show on a board card |
| Webhooks | Addresses told when opportunities and this pipeline change |
| Status | Meaning |
|---|---|
active | In use |
inactive | Not in use, kept |
archived | Put away |
From code
The Pipelines API manages pipelines at /pipeline/api/v2/pipelines and their stages at /pipeline/api/v2/pipelines/stages/:pipeline_uuid. Creating a pipeline needs a name and a status.
Danger
Deleting a pipeline also deletes its stages, its opportunities, their activities and their custom-field data. Archive it instead if you may need the history.
Note
The docs instance has no pipelines. Facts from the Pipelines module reference in the Insites Logic Engine.
Common mistakes
- Deleting a pipeline to tidy the list. Archive it.
- Setting display fields once and expecting them for everyone. They are saved per administrator.
- Expecting a webhook for a stage change on its own. Stage moves send
opportunity_updated.