GoHighLevel API and MCP server Let your AI agent build your HighLevel workflows.

ToolWhat it doesAccess

• list_workflows Lists the workflows in the sub-account with their status. read

  Returns each workflow with its ID, name and whether it is a draft or published. Reads the Workflow List under Automation > Workflows. The IDs feed every other workflow tool.

  MCP callgohighlevel_read → list_workflows

  REST endpointGET https://cotlet.dev/api/v1/gohighlevel/workflows

  Parameters

  Parameters: list_workflows

  Name	Type	Description
  status string	string	Filter by status: draft or published.
  query string	string	Part of a workflow name.

  Example response

  {
    "workflows": [
      {
        "id": "wf_1042",
        "name": "New lead follow-up",
        "status": "published"
      },
      {
        "id": "wf_1077",
        "name": "Missed call text back",
        "status": "published"
      },
      {
        "id": "wf_1103",
        "name": "Review request",
        "status": "draft"
      }
    ]
  }

• get_workflow Returns the triggers and actions of one workflow, in order. read

  Returns the workflow status, every trigger with its settings, and every action in the order the builder shows them, including conditional, drip and goal actions with their branches. Reads what the Workflow Builder shows. Changes nothing, and does not open a published workflow for editing.

  MCP callgohighlevel_read → get_workflow

  REST endpointGET https://cotlet.dev/api/v1/gohighlevel/workflows/{workflow_id}

  Parameters

  Parameters: get_workflow

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.

  Example input

  {
    "workflow_id": "workflow_8c41d2"
  }

  Example response

  {
    "id": "wf_1042",
    "name": "New lead follow-up",
    "status": "published",
    "triggers": [
      {
        "name": "Contact Added",
        "settings": {
          "filter": "Tag is lead"
        }
      }
    ],
    "actions": [
      {
        "id": "act_1",
        "name": "Send Email",
        "settings": {
          "template": "Welcome"
        }
      },
      {
        "id": "act_2",
        "name": "Assign to User",
        "settings": {
          "user": "Maya R."
        }
      }
    ]
  }

• get_workflow_stats Returns trigger and communication-action statistics for one workflow. read

  Returns what Stats View shows. Each trigger has attempted, matched and unmatched contacts; HighLevel counts the last 30 days for triggers. Each communication action has its delivery and engagement numbers. Reads only, so it never turns Stats View into an edit lock for your team.

  MCP callgohighlevel_read → get_workflow_stats

  REST endpointGET https://cotlet.dev/api/v1/gohighlevel/workflows/{workflow_id}/stats

  Parameters

  Parameters: get_workflow_stats

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.

  Example input

  {
    "workflow_id": "workflow_8c41d2"
  }

  Example response

  {
    "workflow_id": "wf_1042",
    "triggers": [
      {
        "name": "Contact Added",
        "attempted": 412,
        "matched": 388,
        "unmatched": 24
      }
    ],
    "actions": [
      {
        "name": "Send Email",
        "sent": 388,
        "delivered": 379,
        "opened": 201
      }
    ]
  }

• list_workflow_versions Lists the saved versions in a workflow history. read

  Returns the versions that the History icon in the Workflow Builder lists, each with an ID and the time it was saved. Use get_workflow for the current steps. Reads only, nothing is restored.

  MCP callgohighlevel_read → list_workflow_versions

  REST endpointGET https://cotlet.dev/api/v1/gohighlevel/workflow-versions

  Parameters

  Parameters: list_workflow_versions

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.

  Example input

  {
    "workflow_id": "workflow_8c41d2"
  }

  Example response

  {
    "workflow_id": "wf_1077",
    "versions": [
      {
        "id": "ver_7",
        "saved_at": "2026-10-20T14:05:00Z"
      },
      {
        "id": "ver_6",
        "saved_at": "2026-10-12T09:41:00Z"
      }
    ]
  }

ToolWhat it doesAccess

• create_workflow Creates an empty draft workflow. write

  Creates the workflow from scratch in the Workflow List and returns its ID. It starts as a draft, so no contact enters it and nothing is sent. It reaches no one, so it needs no confirmation. You remove it from the Workflow List in the app if you do not want it.

  MCP callgohighlevel_write → create_workflow

  REST endpointPOST https://cotlet.dev/api/v1/gohighlevel/workflows

  Parameters

  Parameters: create_workflow

  Name	Type	Description
  name string required	string	Workflow name.
  folder string	string	Name of an existing workflow folder to put it in.

  Example input

  {
    "name": "New lead follow-up"
  }

  Example response

  {
    "id": "wf_1120",
    "name": "New lead follow-up",
    "status": "draft"
  }

• add_workflow_trigger Adds one trigger to a draft workflow. write

  Clicks Add New Trigger, picks the trigger by name, fills in its settings and saves. A workflow can have several triggers, and each starts the workflow when its own conditions are met. Works on drafts only, so no contact is affected. It returns an error that names the field when the builder rejects the settings.

  MCP callgohighlevel_write → add_workflow_trigger

  REST endpointPOST https://cotlet.dev/api/v1/gohighlevel/workflows/{workflow_id}/trigger

  Parameters

  Parameters: add_workflow_trigger

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.
  trigger string required	string	Trigger name as the builder lists it, for example Contact Added or Appointment Booked.
  settings object	object	Trigger settings as the builder shows them, such as filters.

  Example input

  {
    "workflow_id": "workflow_8c41d2",
    "trigger": "trigger"
  }

  Example response

  {
    "workflow_id": "wf_1120",
    "trigger": {
      "name": "Contact Added",
      "settings": {
        "filter": "Tag is lead"
      }
    },
    "saved": true
  }

• add_workflow_action Adds one action to a draft workflow. write

  Clicks the + button in the workflow line, picks the action by name, fills in its settings and saves. Works on drafts only, so the action sends nothing until the workflow is published. Integration-powered actions that need a connected account return an error that says to connect it in the app first.

  MCP callgohighlevel_write → add_workflow_action

  REST endpointPOST https://cotlet.dev/api/v1/gohighlevel/workflows/{workflow_id}/action

  Parameters

  Parameters: add_workflow_action

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.
  action string required	string	Action name as the builder lists it, for example Send Email or Assign to User.
  settings object	object	Action settings as the builder shows them.
  after_action_id string	string	Action ID to add it after. Without it the action goes at the end.

  Example input

  {
    "workflow_id": "workflow_8c41d2",
    "action": "action"
  }

  Example response

  {
    "workflow_id": "wf_1120",
    "action": {
      "id": "act_1",
      "name": "Send Email",
      "settings": {
        "template": "Welcome"
      }
    },
    "saved": true
  }

• set_workflow_status Switches a workflow between draft and published. writeasks first

  Uses the Draft/Publish toggle. A published workflow starts enrolling contacts and runs its actions, which can send email and SMS to your contacts. HighLevel says saving and publishing are separate, so the tool saves any unsaved changes before it publishes. By default you confirm each call; you can switch that off for this tool.

  MCP callgohighlevel_write → set_workflow_status

  REST endpointPUT https://cotlet.dev/api/v1/gohighlevel/workflows/{workflow_id}/status

  Parameters

  Parameters: set_workflow_status

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.
  status string required	string	draft or published.

  Example input

  {
    "workflow_id": "workflow_8c41d2",
    "status": "status"
  }

  Example response

  {
    "workflow_id": "wf_1120",
    "status": "published"
  }

• test_workflow Runs a workflow once on one contact with Test Workflow. writeasks first

  Clicks Test Workflow, selects the contact and clicks Run Test, then reports what the run shows for each step. The run can send messages to that contact. HighLevel notes that a test on a contact is not exact, especially when you reuse the same contact. By default you confirm each call; you can switch that off for this tool.

  MCP callgohighlevel_write → test_workflow

  REST endpointPOST https://cotlet.dev/api/v1/gohighlevel/contacts/{contact_id}/workflows/{workflow_id}/test

  Parameters

  Parameters: test_workflow

  Name	Type	Description
  workflow_id string required	string	Workflow ID from list_workflows.
  contact_id string required	string	ID of the contact to run the test on.

  Example input

  {
    "workflow_id": "workflow_8c41d2",
    "contact_id": "contact_8c41d2"
  }

  Example response

  {
    "workflow_id": "wf_1120",
    "contact": "Sam Rivera",
    "steps": [
      {
        "name": "Send Email",
        "result": "Executed"
      },
      {
        "name": "Assign to User",
        "result": "Executed"
      }
    ]
  }

ToolWhat it doesAccess

• list_funnels Lists the funnels in the sub-account. read

  Returns each funnel with its ID, name and the number of steps. Reads the list under Sites > Funnels. The IDs feed list_funnel_steps, update_funnel_page_seo and publish_funnel.

  MCP callgohighlevel_read → list_funnels

  REST endpointGET https://cotlet.dev/api/v1/gohighlevel/funnels

  Parameters

  Parameters: list_funnels

  Name	Type	Description
  query string	string	Part of a funnel name.

  Example response

  {
    "funnels": [
      {
        "id": "fn_208",
        "name": "Spring Promo",
        "steps": 3
      },
      {
        "id": "fn_215",
        "name": "Free Consultation",
        "steps": 2
      }
    ]
  }

• list_funnel_steps Lists the steps of a funnel with their page name and URL path. read

  Returns each step in the funnel with its ID, page name, URL path and the page title and meta description, empty when none is set. Reads the Steps tab of the funnel. Does not open the page builder.

  MCP callgohighlevel_read → list_funnel_steps

  REST endpointGET https://cotlet.dev/api/v1/gohighlevel/funnel-steps

  Parameters

  Parameters: list_funnel_steps

  Name	Type	Description
  funnel_id string required	string	Funnel ID from list_funnels.

  Example input

  {
    "funnel_id": "funnel_8c41d2"
  }

  Example response

  {
    "funnel_id": "fn_208",
    "steps": [
      {
        "id": "st_1",
        "page_name": "Landing",
        "url_path": "/spring",
        "title": "Spring Promo for Local Studios",
        "description": ""
      },
      {
        "id": "st_2",
        "page_name": "Thank you",
        "url_path": "/thank-you",
        "title": "",
        "description": ""
      }
    ]
  }

• update_funnel_page_seo Sets the title and meta description of one funnel step. write

  Opens the page settings of the step and writes the SEO fields, then saves the funnel as a new version. HighLevel says publishing is a separate click, so the change is not live until publish_funnel runs. It reaches no one until then, so it needs no confirmation.

  MCP callgohighlevel_write → update_funnel_page_seo

  REST endpointPATCH https://cotlet.dev/api/v1/gohighlevel/steps/{step_id}/funnels/{funnel_id}/page-seo

  Parameters

  Parameters: update_funnel_page_seo

  Name	Type	Description
  funnel_id string required	string	Funnel ID from list_funnels.
  step_id string required	string	Step ID from list_funnel_steps.
  title string	string	Page title.
  description string	string	Meta description.

  Example input

  {
    "funnel_id": "funnel_8c41d2",
    "step_id": "step_8c41d2"
  }

  Example response

  {
    "funnel_id": "fn_208",
    "step_id": "st_2",
    "title": "Thank you for booking",
    "description": "Your spring consultation is booked. Check your email for details.",
    "saved": true,
    "live": false
  }

• publish_funnel Publishes the saved version of a funnel. writeasks first

  Clicks Publish, which makes the saved version live for visitors. If the funnel has no domain, HighLevel asks you to attach one; the tool stops and says so instead of choosing a domain. By default you confirm each call; you can switch that off for this tool.

  MCP callgohighlevel_write → publish_funnel

  REST endpointPOST https://cotlet.dev/api/v1/gohighlevel/funnels/{funnel_id}/publish

  Parameters

  Parameters: publish_funnel

  Name	Type	Description
  funnel_id string required	string	Funnel ID from list_funnels.

  Example input

  {
    "funnel_id": "funnel_8c41d2"
  }

  Example response

  {
    "funnel_id": "fn_208",
    "published": true,
    "domain": "promo.example.com"
  }