Automations

Add Relative/Dynamic Date Support to Book Appointment Workflow Action (e.g., +7 days, +1 month from now/current date)
Current Limitation (The Big Pitfall): In workflows, the Book Appointment action is extremely powerful for automating scheduling... but it's currently restricted to static/fixed dates only (e.g., you can only hard-code something like "February 23, 2026 at 2:00 PM"). This creates a major roadblock for almost any real-world automation involving clients or leads: You can't automatically book a follow-up call "7 days from today" after a form submission or opportunity stage change. No way to schedule "next month’s check-in" relative to the contact's last interaction or a custom date field. Impossible to create truly dynamic nurture sequences, onboarding automations, or recurring client touchpoints without manual intervention or clunky workarounds (multiple if/else branches, custom code, Zapier bridges, etc.). Many agencies and users hit this wall when trying to scale client delivery — especially in coaching, consulting, service-based businesses, SaaS onboarding, or any recurring appointment model. Proposed Improvement (What We Need): Please add support for relative/dynamic date calculations in the Book Appointment action's date/time picker, similar to how Date/Time Formatter, Wait steps, and other actions already handle offsets. Ideal options in the date selector: Fixed/Static date (keep existing) Relative to current date/time — e.g., +X days/hours/weeks/months from "Now" (workflow execution time) Relative to a custom field/date value — e.g., +7 days from {{contact.custom_field_last_call_date}} or +30 days from {{ opportunity.date _created}} Relative to another event — e.g., +1 week after a previous appointment (if chaining multiple bookings) Bonus: Ability to combine with Date/Time Formatter output for advanced logic (add business days, skip weekends, etc.) This would unlock: Automated follow-up bookings ("Book your next session exactly 1 week later") Dynamic onboarding sequences Recurring client check-ins without manual calendar edits Much more powerful AI/Conversation/Workflow automations tied to calendars Hundreds (if not thousands) of agencies would benefit immediately — this feels like low-hanging fruit to make GHL's automation even more competitive with tools like Calendly + Zapier combos, but native and seamless. Use Case Examples: Lead submits form → Workflow books discovery call for "next Tuesday at earliest available slot after 48 hours" Opportunity moves to "Closed Won" → Auto-book "30-day check-in" relative to close date Client completes milestone (tagged) → Schedule review call "+10 business days" from tag date If this already exists in some hidden way (or via Set Event Start Date + other actions), please link docs — but from extensive testing and meeting with support, it seems unavailable for direct booking. Upvote if you’ve run into this limitation or want more flexible, hands-off client scheduling automations! Thanks for considering — this would be a game-changer for scaling service delivery.
1
·
New Feature
Add “Webhook Response” action to return JSON directly to incoming webhooks (with header support)
GoHighLevel currently allows capturing inbound webhooks, but there is no way to send a response back to the original webhook request. Many modern API integrations require returning a JSON response on the same HTTP request, with headers such as: Content-Type: application/json Because GHL does not provide any “Response” or “Return to Webhook Source” action, these integrations are not possible today. Why this is important: Increasingly, external services expect automation platforms to: Receive an inbound webhook Process data Send back a synchronous JSON response to the same request A current example is the Fonio Voice Assistant, which personalizes phone calls based on data returned by the webhook consumer. If GHL cannot return a JSON response, the integration fails completely. Other platforms (Make, Zapier, n8n, etc.) support webhook responses — adding this to GHL would unlock many real-time integrations. Requested Feature: Add an action in Workflows: “Webhook Response” / “Return to Source” This action should: Return data to the original incoming webhook Allow setting HTTP headers (especially Content-Type: application/json) Support JSON bodies Ideally allow selecting status codes (200 default) Additional Enhancements Header editor (Content-Type, charset, custom headers) Ability to handle multiple response formats (JSON, text, XML) Logging of the returned response for debugging Example Use Cases: Voice assistants needing synchronous data responses Payment gateways requiring acknowledgment payloads SaaS tools that validate events based on returned JSON Real-time bot or messaging platforms Systems that require returning temporary tokens or challenge validations Impact Implementing this feature would: ✔ Enable real-time integrations ✔ Bring GHL in line with other automation platforms ✔ Prevent users from needing external servers or proxies ✔ Greatly expand GHL’s API interoperability This would be a high-value enhancement for agencies, automation builders, and SaaS integrators.
0
·
New Feature
Load More