Each pipeline in Bigin represents a distinct business process, such as lead qualification or post-sale onboarding. Connected Pipelines lets you designate a target pipeline so that when a record reaches a specified closing stage in the source pipeline, Bigin automatically creates or moves the record into the opening stage of the linked pipeline. The connection is configured at the pipeline level in Bigin’s settings, and the same contact or deal record carries its history across both processes.
Use Connected Pipelines when your business has sequential processes that must share the same underlying contact or company record but are managed by different teams. Common pairs include sales-to-onboarding, trial-to-subscription, or inquiry-to-support. Avoid this feature if your processes are parallel rather than sequential, or if your team only runs a single end-to-end pipeline where all stages already belong to one flow.
Connected Pipelines is available in Bigin’s Team plan and above, where Team Pipelines itself is enabled. You can only connect pipelines within the same Bigin organisation. The trigger is the record reaching a specific winning or closing stage, so stage naming matters: ensure your terminal stage is accurately marked as a closing stage before configuring the connection. Records that are lost or deleted in the source pipeline do not carry over to the destination.
Each pipeline can be connected to one destination pipeline at a time in Bigin. If you need records to branch into multiple downstream processes, you would need to use Bigin’s Workflows or Signals to trigger those additional actions once the record enters the next pipeline.
No. Connected Pipelines moves or links the existing record to the next pipeline rather than creating a copy. The contact’s full activity history, notes, and attachments remain intact and visible in the destination pipeline, ensuring continuity across teams.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.