Per-tenant pipeline configuration stored alongside the credentials. Live pipelines are fetched from the CRM to drive the dropdowns and the stage mapping table. Both credentials and pipeline configuration are required before the connection counts as live.
Also called: which pipeline do leads come from · map my CRM stages · pipeline id
- 1Pipelines load once credentials are present; failures show a specific error rather than an empty dropdown.
- 2Per-internal-stage assignments are edited inline and saved with the pipeline choice.
- 3A manual-ID mode lets an admin paste a pipeline id directly when the dropdown is missing it — a pipeline id alone is enough for the polling sync to fetch opportunities.
The manual escape hatch has an explicit rationale in the code: a token's scope may be limited to a subset of pipelines, or the dropdown may be stale, and without a way in the connection simply cannot be completed. Requiring both credentials and pipeline config before marking the connection live prevents a half-configured integration reporting itself as connected.
- A restricted token hid the pipeline the tenant needed, with no way to proceed.
- A connection could report itself live while missing its pipeline configuration.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →