Workflow Automation

This wraps HubSpot's v4 flows API through the agent CLI (the `hubspot` command, not the `hs` developer CLI). You get list, get, create, update, and delete for workflows. The update is a full PUT, so you fetch the current JSON, edit it, then push it back with the revisionId intact. No search command exists, so finding by name means piping list output through jq. The create dry run doesn't validate schema, only that your JSON parses, which is annoying. Branching and convergence work by pointing nextActionId references at shared actions. Safest path is to get an existing workflow as a template rather than hand writing the body from scratch.

skills.sh installs: 1.9K
GitHub stars: 29
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add hubspot/agent-cli-skills --skill workflow-automation --agent claude-code

Installs into .claude/skills of the current project.

Files

Which CLI

Two different HubSpot CLIs share a confusing resemblance — don't mix them up:

hubspot — the HubSpot agent CLI that this skill library targets. It manages CRM data and automation, and it does have native workflow commands: hubspot workflows list|get|create|update|delete.
hs — the HubSpot developer CLI (@hubspot/cli), for building dev projects: themes, modules, serverless functions, UI extensions, and private apps (hs project, hs upload, hs create). It does not create or manage workflow records.

To create or manage a workflow, use hubspot workflows ... — not hs.

If anything here ever drifts, hubspot workflows --help and hs --help are authoritative.

Resources

File	When to use
`resources/workflow-json-reference.md`	Body shape for create/update — the action graph, branching/convergence, enrollment, full-PUT pitfall
`resources/example-contact-flow.json`	Minimal valid `CONTACT_FLOW` skeleton for `hubspot workflows create --file`
`resources/example-branching-flow.json`	Illustrates branch convergence — two paths pointing `connection.nextActionId` at one shared downstream action