Command note: A draft workflow looks finished in the builder and does nothing in the account.
Drafts pile up quietly. Someone builds a follow-up, gets pulled away, and the client assumes it has been running for months. The fix starts with a list, not a rebuild.
Paste this into Claude with GHL Command connected:
"List every workflow in this sub-account using get_workflows. Group them by status: draft and published. For each draft, show the name, when it was created and when it was last updated. Flag drafts that have not been touched in 30+ days, and drafts whose name suggests something the client expects to be live (follow-up, reminder, nurture, review request). Read only. Do not publish, edit or delete anything."
What you get back:
• A clean count of live versus parked automations
• The stale drafts nobody remembers starting
• The ones that look like a promise the account is not keeping
What to do with the list:
1) Ask the client which automations they believe are running, then compare against the list
2) Finish and test the drafts that matter, then publish them by hand
3) Rename parked drafts with a PARKED prefix and a one-line reason
4) Clear out the true leftovers once you have a copy
Publishing stays a human step. Read the trigger and the first message one more time before anything goes live.
If it is not published, it is not working. Know which ones those are.