24d • General discussion
Found a bug while using DM workflow
DM to Jerry Relth:
Hey Jerry, found something in GHL Command you might want to know about. Not a complaint, the tool has been great.
I built an Instagram comment to DM workflow with the MCP. Ran validate_workflow on it and got back status: ok, 6 references scanned, 0 issues, 0 warnings. Clean.
Then I published it and ran a real test. Comment fired, public reply posted, DM delivered, tag applied, lead source set. But the Create/Update Opportunity step did nothing. No opportunity in the pipeline, no opportunity on the contact. The workflow just carried on to the next action like nothing happened.
Turned out the action only had pipelineId and pipelineStageId set. Per HighLevel's own doc for that action, it also requires Opportunity Name, Opportunity Source, and Status. Three mandatory fields missing. Nothing to write, so it no-oped.
The validator is checking that the IDs it references exist. It is not checking that required fields are present. So a workflow can come back 0 errors, 0 warnings and still be missing the fields it needs to actually do anything.
Two reasons I thought you'd want it.
First, this is exactly the silent-failure case the tool is supposed to catch, and I'd been treating a clean validation as proof the build was sound.
Second, that action type is internal_update_opportunity, and HighLevel's docs say Create/Update Opportunity is being phased out in favor of separate Create Opportunity and Update Opportunity actions. So anything the builder emits with it is on a clock.
Workflow ID if it helps: a5017b5a-5076-4026-a9ba-67882691c7ca.
0
2 comments
Found a bug while using DM workflow
Suggested communities
Powered by