Skip to content
My GoHighLevel MCP
Guide

Build a lead follow-up workflow by describing it to Claude

Describe the automation in a sentence, check the draft Claude builds, then publish. A practical walk-through for new-lead follow-up.

Product team

3 min read

Most agencies have the same handful of automations in every client account: a welcome text when someone fills in a form, a reminder before an appointment, a nudge when a lead goes quiet. Building them by hand means a lot of clicking through the workflow builder. With Claude connected to GoHighLevel, you can describe the workflow instead and let Claude assemble it.

Start with one clear sentence

Claude works best when the request says what starts the workflow and what should happen, in order. For example:

In Summit Roofing, build a workflow: when someone submits the free quote form, tag them "quote-request", wait 10 minutes, then send them a text saying we'll call them today.

That sentence has everything Claude needs: the sub-account, the trigger, and three steps. If you work in more than one sub-account, always name it, or ask Claude to switch to it first.

Claude builds a draft, not a live automation

Claude saves the new workflow as a draft. Nothing fires until you publish it, so you can open GoHighLevel and check the trigger and each step before a single text goes out. Claude will usually summarise what it built, something like:

Built "Quote request follow-up" as a draft: trigger Form submitted (Free quote) → add tag quote-request → wait 10 minutes → send SMS. Publish it?

Read that summary carefully. If the wording of the text is wrong, or the wait should be longer, just say so:

Make the wait 5 minutes and sign the text from Jake.

Publish when you're happy

Once the draft looks right, ask Claude to publish it. You can also ask it to put a few existing contacts into the workflow straight away, for example the leads who submitted the form this morning before the automation existed.

Claude checks with you before anything that sends messages, so you will get a clear question before those contacts receive a text.

Check how it's running

A day later, ask:

How is the quote request workflow doing? Any errors in its logs?

Claude can read a workflow's steps and its run logs, so you find out quickly if a step is failing, for instance because a contact has no phone number.

Reuse it in other sub-accounts

Once a workflow works in one client account, you can ask Claude to build the same thing in another sub-account, adjusting the details:

Build the same quote request workflow in Bright Smile Dental, but for the "Book a check-up" form and signed from the front desk.

A few tips

  • Keep one workflow per job. Two small workflows are easier to check than one large one.
  • Test on a test contact first. Put yourself into the workflow and watch the steps arrive.
  • Name things clearly. Ask Claude to use names your team will recognise in GoHighLevel.
  • Everything is logged. Every change Claude makes appears in the panel's Activity log, with who asked and in which sub-account.

If you haven't connected Claude yet, the five-minute setup guide walks you through it.

  • #workflows
  • #automation

Written by

Product team

Guides and product news

The people who build My GoHighLevel MCP. We write practical guides for agencies and businesses running GoHighLevel from Claude, and we keep them up to date as the product changes.

More from Product team →

Keep reading

All articles →