One policy module answers 'do we write pipeline state to the CRM?'. Server-side stage automation consults it before mirroring an advance. Setting the env flag to 0 turns the mirror off at runtime; the default is on to preserve production behaviour.
Also called: mirror stage to CRM · keep GHL in sync · GHL_STAGE_MIRROR_ENABLED
- 1A stage advance fires server-side.
- 2isStageMirrorEnabled() is consulted.
- 3When on, the opportunity's stage is updated in the account's CRM pipeline.
- 4When off, nothing is written and the platform stays authoritative.
The module exists to resolve a contradiction, stated in its header: 'Two historically separate gates existed and contradicted each other' — the browser engine's compile-time false and the server automation's independent mirror. Consolidating them means the answer to 'does this app write pipeline state to the CRM?' has exactly one place to look, and 'When the CRM port lands, both gates collapse into the adapter's optional mirrorStage capability.'
- Two contradictory gates governed the same question.
- Disabling CRM writes required a code change and a deploy.
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 →