M
Marc Böhret
GoHighLevel currently does not provide a reliable way to set default values for custom fields at the moment an object is created (e.g., Contact, Opportunity). This makes it difficult to guarantee a correct initial state for automations.
Because multiple workflows can run in parallel and workflow execution is not transactional (especially with event-based splitting), missing default initialization can lead to race conditions and inconsistent or incorrect outcomes.
⸻
Problem
  • No native way to define default values for custom fields on object creation
  • Workflows can trigger simultaneously and evaluate fields before they are properly initialized
  • Event-based splitting + parallel workflows can produce inconsistent results
  • There is no built-in “transaction-like” mechanism to ensure initialization is complete before logic runs
⸻
Expected Behavior
  • Ability to set default values for custom fields when an object is created (e.g., default stage flags, booleans, statuses, timestamps, counters, etc.)
  • Ability to coordinate workflow execution so that downstream logic only runs after initialization is complete
⸻
Proposed Solutions / Feature Requests
1. Default Values on Creation
Add an option to define default values for custom fields (per object type) that are automatically applied on object creation.
2. Workflow Synchronization / Gating (Wait-Until)
Provide workflow actions/conditions that enable safe sequencing, such as:
  • Wait until tag is added (e.g., an “initiated” tag)
  • Wait until workflow step completed / Wait until workflow finished (a “workflow done” signal)
  • Optionally: “Wait until field initialized” / “Wait until field equals X”
⸻
Impact / Use Case
  • Prevents race conditions in parallel automations
  • Ensures deterministic initial states for downstream logic
  • Reduces reliance on fragile workarounds (manual delays, duplicate workflows, excessive tags)
  • Improves reliability when multiple workflows are triggered on the same creation event