A compile-time gate disables every outbound pipeline write: creating opportunities, moving stages, updating value and deleting opportunities are all guarded off. Inbound fetching, contact create/lookup (the messaging identity), notes and customer messaging stay enabled because they are orthogonal to pipeline state.
Also called: one-way sync · stage snap-back · card moves back on its own
- 1GHL_PIPELINE_OUTBOUND_ENABLED is false in the sync engine.
- 2createOpportunity, moveOpportunityStage, updateOpportunityValue and deleteOpportunity short-circuit.
- 3fetchContacts, fetchPipelineOpportunities, getOrCreateContact, addNote, sendEmail and sendSms remain live.
- 4The single sanctioned outbound pipeline write lives outside this gate, in the stage-mirror policy.
The rule and its cause are recorded together: 'two-way pipeline sync was the root of stage snap-back, dedup conflation, and "card reappears after remove" bugs, and it blocked building custom pipeline logic (our stages never matched GHL's). Cutting outbound pipeline writes makes our DB authoritative and the board predictable.'
- Two-way sync caused stage snap-back and resurrected removed cards.
- Custom pipeline logic was impossible while the CRM's stage model had to be mirrored.
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 →