One workflow, not fifty

Lesson 2 of 7 · Module 04 · The Comment-to-Client Machine

The way I had seen comment automation taught: the trigger binds to a specific post, so the post has to exist first, and every new post needs its own copy of the workflow. Fifty posts, fifty workflows. A clone-and-rebind chore every time you publish.

That was true once. It is not true now, and knowing the difference saves you from maintaining a workflow farm forever.

GHL has native comment triggers for Instagram and Facebook. No third-party connector. And both triggers can live in the same workflow, so one workflow covers both platforms. On each trigger, three settings do all the work:

Page is: your connected page.

Post Type: Published Post. This is the setting that changes everything. Published Post means any post on the page. Every post you have made and every post you will ever make. The other option, Custom Post, scopes the trigger to one specific post URL. Custom Post is the old per-post way. It still exists, and it is fine if you ever want a keyword that only works on a single post, but you do not need it for the main machine.

Keyword filter: Contains Phrase, set to your word. Ours is ATLAS.

That is it. One master workflow, published once, fires on the keyword across every post forever. No clones. No rebinding. No waiting for a post to exist before you can wire it.

We published ours and verified it through the API afterward: both triggers active, post type set to published, keyword bound on both. One workflow, both platforms, every post.

Now the trap that cost us real time on build day.

When I opened the Instagram comment trigger, the page picker said "No result found." Our accounts were connected. I could see them in the Social Planner. Posts were already scheduled through it. And the trigger could not see the page at all.

Here is the gotcha: the comment triggers do not read the Social Planner connection. They read the Facebook connection under Settings, then Integrations. Those are two different connections with different permissions. We had connected the planner and never done the Integrations connect. The moment we linked the page at Settings, Integrations, the picker populated. If your picker is empty and you are sure your accounts are connected, this is almost certainly why.

Two honest notes before you build.

First, case sensitivity. GHL's docs say Contains Phrase matches regardless of case, so a lowercase "atlas" should fire a workflow set to ATLAS. I have not proven that live yet. Our first live comment test includes a lowercase comment for exactly this reason. Until you have proven it on your own page, write the CTA in caps, exactly the way you want it typed, and assume nothing.

Second, the boundary. This is Instagram and Facebook only. GHL has no native comment trigger for TikTok or YouTube. If someone promises you native comment-to-DM on those platforms inside GHL, they are wrong or they are selling a third-party bridge.

Build the master workflow once. Set Published Post and Contains Phrase on both triggers. Then go make content, because every future post is already wired.

Next lesson: the DM itself, and the version of it I almost shipped that would have messaged nobody.