Automations

I have multiple opportunities per contact, and each opportunity has a linked estimate (or invoice). Once a customer accepts/declines estimate, hence triggering automation, I should be able to find the linked opportunity and update its status. Right now I can only find latest or earliest, which does not work for when you have multiple opportunities from same contact.

I want to be remembered onv=ce it is time for a business owner to take care of their parking lot. I want it to be light and more of a reminding feeling im giving them so they are always thinking about making their business looking better.

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

Right now, the inbound webhook cannot parse the column details from the lead form webhook from Google Ads. It parses everything else properly to map the sub-headings, just not the important stuff like FIRST NAME, PHONE, EMAIL, etc. This is the sample payload from Google Ads: { "lead_id": "TeSter-123-ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-0123456789-AaBbCcDdEeFfGgHhIiJjKkLl", "user_column_data": [ { "column_name": "User Email", "string_value": " test@example.com ", "column_id": "EMAIL" }, { "column_name": "User Phone", "string_value": "+16505550123", "column_id": "PHONE_NUMBER" }, { "column_name": "City", "string_value": "Mountain View", "column_id": "CITY" }, { "column_name": "First Name", "string_value": "FirstName", "column_id": "FIRST_NAME" }, { "column_name": "Last Name", "string_value": "LastName", "column_id": "LAST_NAME" }, { "string_value": "Example answer", "column_id": "what_type_of_tree_services_are_you_needing?" } ], "api_version": "1.0", "form_id": 317442547680, "campaign_id": 22404897829, "google_key": "clickrdigital", "is_test": true, "gcl_id": "TeSter-123-ABCDEFGHIJKLMNOPQRSTUVWXYZ-abcdefghijklmnopqrstuvwxyz-0123456789-AaBbCcDdEeFfGgHhIiJjKkLl", "adgroup_id": 20000000000, "creative_id": 30000000000, "headers": { "host": " services.leadconnectorhq.com ", "cf-ray": "9be8f2217b73454f-ORD", "x-forwarded-for": "192.178.15.1,10.10.1.21", "cdn-loop": "cloudflare; loops=1", "cf-connecting-ip": "192.178.15.1", "accept-encoding": "gzip, br", "cf-ipcountry": "US", "x-forwarded-proto": "https", "content-length": "904", "content-type": "application/json", "cf-visitor": { "scheme": "https" }, "user-agent": "Google-Ads-Notifications", "x-envoy-external-address": "10.10.1.21", "x-request-id": "3bf4adb3-c1e8-40a2-8866-d589191df16c", "x-envoy-attempt-count": "1", "x-forwarded-client-cert": "By=spiffe: //cluster.local/ns/default/sa/default-automation-workflows;Hash=0d6e49a9aab5d0b610fb3aef36fcdf30411670fcf709a81ca10d83d4556868c0;Subject=\"\";URI=spiffe://cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account ", "x-b3-traceid": "a6ef57e72e6a16f9f65a1ab266ec7f80", "x-b3-spanid": "1c53db2a4b82dcc4", "x-b3-parentspanid": "f65a1ab266ec7f80", "x-b3-sampled": "0" } }

It would be wonderful if replies to emails form workflow would have a dynamic reply-to. Lets say I am sending 100 contacts an email campaign via workflow. I would love for each of them to be able to click "reply" and have their assigned user's email auto-populate in the CC or To portion of their email.

Right now, a contact’s workflow history is one long list, and the only grouping is Active vs Past Workflows. It’s hard to find the important workflows that actually matter, and I don’t want to sift through minor backend stuff like notifications or updating custom fields. Custom folders or collapsible sections would make it much easier to find what matters.

Problem Summary When workflows/automations update contacts, the Audit Logs do not show which workflow performed the change. Instead, admins only see that a field changed on a contact, often with no user attribution (system/automation) and no workflow name or link. With hundreds of active workflows, the current workarounds (naming conventions, time-based correlation, tags/helper fields, etc.) become: Operationally untenable Error-prone Time-consuming This directly impacts: Auditability – It’s difficult or impossible to answer “Which workflow changed this contact field and why?” in a reliable, repeatable way. Compliance – For regulated industries or strict internal controls, you need a clear, defensible trail showing which automated process made which change. Debugging & QA – When a workflow misbehaves, tracking down the exact automation responsible for a change is far harder than it should be. Current Behavior Audit Logs (Settings › Audit Logs) focus on: User-initiated changes and some system-level events. Showing what changed on a record and when. For automation-driven contact changes: The log shows the field-level change (e.g., tag added, stage changed, DND updated). The actor is often a system/automation, not a named user. No workflow name or direct link is included in the log entry. As a result, with many workflows in play, there is no scalable, built-in way to attribute a specific contact change to a specific workflow. Why Existing Workarounds Don’t Scale Common suggestions today include: Strict workflow naming conventions. Centralizing ownership of certain fields into a single “owner” workflow. Using tags or custom fields as “breadcrumbs” (e.g., Changed-by:WF-XYZ). Time-window correlation between logs and known workflow schedules. These may work for a small number of automations, but with hundreds of workflows: The mental and operational overhead becomes too high. Breadcrumb tags/fields can clutter data and still don’t provide a clean, authoritative audit trail. Time-based correlation is fragile when multiple workflows can run around the same time. In short: these are stopgaps, not a sustainable solution for large, automation-heavy accounts. Requested Enhancements Include Workflow Name in Audit Logs for Automation-Driven Changes For any contact (or other object) change initiated by a workflow, add: Workflow name (e.g., WF – Lead Nurture – Stage Updates). Optionally, the specific action step name/ID within the workflow. Display this in the Audit Log entry so admins can immediately see: “Field X changed from A → B by Workflow Y.” Add a Direct Link from Audit Logs to the Workflow In each relevant Audit Log entry, include: A clickable link that opens the corresponding workflow in the builder. This would dramatically speed up: Root-cause analysis. Debugging misconfigured logic. Reviewing the exact automation that caused a change. Clear Actor Attribution for Automations Distinguish clearly between: Human users (e.g., “Edited by John Doe”), and Automations (e.g., “Edited by Workflow: [Workflow Name]”). This helps both operational teams and auditors understand whether a change was manual or automated. Expose Workflow IDs in the Automation Builder For each automation within the automation builder: expose the workflow ID in the workflow settings UI this would allow for effective cross referencing with the audit logs (Optional, but powerful) Filter/Reporting by Workflow in Audit Logs Ability to filter Audit Logs by workflow: “Show me all changes made by Workflow X in the last 30 days.” This would support: Change-impact analysis before deprecating or modifying a workflow. Compliance reviews for specific automations. Impact & Justification Scale: In environments with hundreds of workflows, automation is the backbone of operations. Without workflow-level attribution, the more you automate, the harder it becomes to understand and trust your data. Audit & Compliance: Many businesses must be able to answer: “Who or what changed this field?” “Why was this consent/DND/pipeline status updated?” Today, the answer is often “a system process, but we can’t definitively say which one,” which is not sufficient for serious audits or regulatory reviews. Risk Reduction: Misconfigured workflows can silently change large volumes of data. Without clear attribution, detecting and correcting these issues is slow and risky. Workflow names/links in Audit Logs would significantly reduce time-to-diagnosis and blast radius of automation errors. User Trust & Adoption: Strong, transparent auditability encourages customers to: Use more automation. Trust the system with more critical processes. Conversely, opaque automation behavior can limit adoption in risk-sensitive organizations.

In GoHighLevel workflows, date conditions are currently limited to calendar-based logic (e.g. “within 1 day”, “tomorrow”) or static before/after comparisons. There is no way to perform true rolling date and time logic using If/Else conditions, such as: • “Is this contact within 24 hours of an event start?” • “Is NOW greater than (Event DateTime − X hours)?” While relative datetime offsets are supported in Wait Until actions (e.g. “wait until Event Start minus 24 hours”), this same logic cannot be used in If/Else conditions for classification, branching, or immediate decision-making. This limitation makes it difficult to build accurate event funnels, deadline cutoffs, fairness-based access rules, or urgency messaging without relying on workaround patterns (Wait Until steps, hard-coded dates, or external automation tools). Feature request: add true datetime arithmetic and rolling time-window comparisons (hours/minutes, not just days/weeks) to workflow If/Else conditions, ideally supporting dynamic offsets from custom fields or appointment times.

We track our campaign conversions through the a custom multi-select field. When a contact starts a new campaign, ideally we would append a new custom value into the multi-select field however I have since learnt that this value overwrites the existing fields causing a loss in our data. This is a very annoying limitation that needs to have the option to append values rather than fully overwriting.

the formatting in the emails sometimes does NOT actually show up until we test the email. Please add a simple preview button before testing it out