J
James Hurst
## The Ask
Expose workflow execution logs, audit logs, and workflow error events through the public REST API (PIT-authenticated). Currently these are UI-only — no programmatic access exists.
### Specific endpoints requested:
  1. GET /workflows/{workflowId}/executions
    — List execution history with filters (status: active/completed/failed, contactId, dateRange, pagination)
  2. GET /audit/search
    — Query audit log entries by module, action type, date range, and user
  3. Webhook event: workflow.action.failed
    — Real-time webhook trigger when any workflow action fails, including: workflow name/ID, action step name, contact ID, error message, timestamp
## Why This Matters
Agency operators managing multiple sub-accounts have no way to programmatically monitor workflow health.
We are forced to manually click into each workflow, check the Execution Logs tab, and visually scan for red error highlights. That does not scale.
Here is what we would build with API access:
  • Automated error alerting
    — A script that checks for failed workflow actions across all sub-accounts every hour and sends a Slack/SMS alert: "Workflow Contact Us Form failed on step Send Welcome Email for contact John Smith at 2:15 PM. Error: invalid email address."
  • Cross-workflow health dashboards
    — Aggregate execution stats (success rate, failure rate, avg completion time) across all workflows in a location. Right now you can only see one workflow at a time in the UI.
  • Audit trail integrations
    — Pipe audit log data into external compliance/logging systems (Datadog, Supabase, custom dashboards). The 60-day retention limit in the UI means audit data is permanently lost after 2 months — API access would let agencies archive it.
  • Proactive CRM monitoring
    — Detect when a workflow silently fails (e.g., a welcome email never sent, a tag never applied) before the customer notices. Right now errors go undetected unless someone happens to check.
## Current Workarounds (and why they fall short)
  1. Email error notifications
    — GHL sends error emails, but they are unstructured prose. Parsing emails for monitoring is fragile and slow.
  2. Adding webhook steps to every error branch
    — Works but requires manually editing every workflow step. For an account with 20+ workflows and 100+ action steps, this is days of work and creates maintenance overhead.
## The Opportunity
  • Unlock a new category of monitoring/observability marketplace apps
  • Differentiate HighLevel for agencies managing 10+ sub-accounts at scale
  • Reduce support tickets from "my workflow broke and I did not know for 3 days"
  • Enable the same programmatic access pattern that already exists for contacts, conversations, and pipelines
  • Let agencies archive audit data beyond the 60-day UI retention window
## Related Requests
  • "In Depth Audit Logs" (ideas board — Reporting category)
  • "Audit Logs — Custom Fields" (ideas board — CRM category)
This would be a game-changer for any agency running automations at scale.