Home/HighLevel/Features/Workflows/How to create and publish workflows via the HighLevel API

Workflows and Automation

How to create and publish workflows via the HighLevel API

In short

The Workflows API lets developers manage HighLevel automations from external applications. It supports creating, validating, publishing, updating and deleting workflows, as well as retrieving execution logs and performance statistics, all without using the visual builder.

AreaWorkflows · Developer Resources
Used forMarketing agency, SaaS startup, Real estate brokerage
Setup steps5 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Agencies that run many client subaccounts benefit because they can deploy a standard workflow to each account with a single API call.
  • Developers building integrations can automate workflow creation and monitoring directly from their own systems.

02Workflows API, explained

The Workflows API provides endpoints for full lifecycle management of HighLevel workflows. You can fetch supported step types, validate a workflow definition, create the workflow in draft mode, update its definition, change its publish status, and delete it when no longer needed.

The API lives in the HighLevel platform under the private integrations area. After enabling the appropriate scopes and generating an access token, you send requests to the services.leadconnectorhq.com domain with a v3 version header. Responses include workflow IDs, version numbers and validation details that guide further actions.

03How businesses use the Workflows API

  • Marketing agency. The agency enables the Workflows API for each client subaccount, pulls a template definition, creates a matching workflow via the API, and publishes it. This lets the agency roll out identical lead nurture automations across all clients without manual setup.
  • SaaS startup. When a new customer signs up on the startup's website, the integration builds a custom onboarding workflow definition, validates it, creates the workflow in draft, and publishes it through the API, delivering a ready to run sequence for each user.
  • Real estate brokerage. The brokerage's internal system calls the Get Workflow Logs endpoint each night to retrieve execution records. It then uses the aggregated statistics endpoint to generate a report of step failures, helping the team address automation issues promptly.

04The numbers and rules that matter

  • Private beta access required; otherwise a 403 error with code WORKFLOW_API_NOT_ENABLED_FOR_LOCATION is returned.
  • Version header required: V3.
  • Rate limits: Standard public API 100 requests per 10 seconds and 200,000 per day per subaccount.
  • Workflow reads 30 requests per 10 seconds per subaccount.
  • Workflow writes 10 requests per 10 seconds per subaccount.
  • Workflow logs 20 requests per 10 seconds and 60 per minute.
  • Workflow log statistics 5 requests per 10 seconds, 10 per minute, and 1,000 per day.
  • Execution log date filters limited to 30 day ranges; history up to 60 days.

05Before you start

  • Confirm the subaccount is part of the private beta for the Workflows API.
  • In Settings > Private Integrations, create a private integration and enable the required workflow scopes.
  • Generate an access token and store it securely.

06How to set up and use the Workflows API in HighLevel

Create and publish a workflow using the API

  1. Call the Get Step Types endpoint to list all supported triggers, actions and required properties.
  2. Assemble a workflow definition that includes the name, selected triggers, actions, connections and any settings.
  3. Submit the definition to the Validate Workflow Definition endpoint and review any errors or warnings.
  4. Send the definition to the Create Workflow endpoint; the workflow is saved as a draft.
  5. Change the workflow status to "published" via the Update Workflow Status endpoint.

07What it looks like in HighLevel

08Settings that matter

  • View Workflows. Allows read only access to workflow details and the list of available step types.
  • Edit Workflows. Grants permission to create new workflows, validate definitions and modify existing ones.
  • Publish Workflows. Enables changing a workflow’s status between draft and published.
  • Delete Workflows. Permits removal of existing workflows from the account.
  • View Workflow Logs. Provides access to execution logs and detailed run information for a workflow.

09Things to know before you rely on it

  • The API is in private beta; only selected subaccounts receive access, otherwise a 403 error with code WORKFLOW_API_NOT_ENABLED_FOR_LOCATION is returned.
  • Standard public API limits are 100 requests per 10 seconds and 200,000 per day per subaccount.
  • Workflow reads are limited to 30 requests per 10 seconds; writes are limited to 10 requests per 10 seconds per subaccount.
  • Log requests allow a maximum date range of 30 days and pull data from the most recent 60 day history.
  • Version conflict protection rejects updates that do not include the latest workflow version.

10If something goes wrong

  • Receiving a 403 response with WORKFLOW_API_NOT_ENABLED_FOR_LOCATION. Verify that the subaccount has been granted private beta access to the Workflows API.
  • HTTP 429 response indicating rate limit exceeded. Reduce request frequency to stay within the documented limits and implement retry logic with back off.

11How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

When you need to roll out the same automation to dozens of client accounts, doing it manually in the builder becomes a bottleneck. The Workflows API lets you push a template workflow to every subaccount with a single call.

The first setting I would lock down is the scope permissions in Settings > Private Integrations. Make sure the integration only has the read, write or publish scopes it truly needs. That prevents accidental deletions or unwanted changes while you get the automation up and running.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about the Workflows API.

Who can access the Workflows API?

Only subaccounts that have been approved for the private beta can use the Workflows API. Contact HighLevel Support to request access.

Why am I receiving a 403 error?

A 403 response with the code WORKFLOW_API_NOT_ENABLED_FOR_LOCATION means the subaccount does not have private beta access.

Can I create and publish workflows entirely through the API?

Yes. Eligible integrations can define a workflow, validate it, save it as a draft and then publish it using the API.

Can I edit an existing published workflow?

Yes. Change the workflow to draft status, retrieve its current definition, apply updates, validate again and publish.

Does the API prevent conflicting workflow updates?

Yes. Including the latest workflow version in the update request ensures outdated changes are rejected.

Can I view workflow execution history?

Yes. Use the Get Workflow Logs endpoint for detailed runs and the Get Workflow Log Statistics endpoint for aggregated data.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.