You Can Now Build HubSpot Workflows with Natural Language Here's How We Did It

There's a moment in every RevOps leader's career where they realize the bottleneck isn't strategy, it's execution. You know exactly what automation you need to build. You can describe it in a single sentence. But turning that sentence into a live HubSpot workflow has always required clicking through a builder, configuring triggers, adding delays, wiring actions together, and hoping nothing breaks.

That bottleneck just got removed.

HubSpot recently opened up its Automation v4 API for workflow creation, and when you pair it with Claude and the Claude in Chrome extension, the result is something that genuinely surprised us: you can describe a workflow in plain English and have it built, configured, and turned on in HubSpot in under a minute. No clicking. No builder. Just a single prompt.

Here's how we set it up, what we built, and why this matters for revenue teams everywhere

HubSpot's New Workflow API: What Changed and Why It's a Big Deal

HubSpot has long been the platform of choice for revenue teams who want powerful automation without needing an engineering team. But building workflows has always been a UI-first experience, which means it's been a clicks-first experience.

With the release of the Automation v4 API, HubSpot has opened the door to programmatic workflow creation. You can now make an API call and create a fully configured, immediately active workflow complete with triggers, delays, branching logic, email sends, task creation, property updates, and more.

This isn't just a developer feature. When paired with an AI layer that can translate plain English into the required API payload, it becomes something that any RevOps practitioner can use.

The implications are significant:

• Speed: Workflows that used to take 15–20 minutes to configure manually can be created in seconds

• Consistency: Every workflow is built programmatically, following the same steps each time.

• Scale: Complex workflows that previously took significant effort to configure manually can now be built in a single prompt.

• Accessibility: You don't need to know JSON or be an API developer to take advantage of this; you just need to be able to describe what you want

HubSpot deserves real credit here. Opening up this API layer is a meaningful commitment to the developer and practitioner ecosystem. It signals that HubSpot sees its platform not just as a UI to click through, but as infrastructure that can be composed, extended, and automated, and that's exactly the right direction for a platform powering modern revenue operations

What It Means to Build Automation with Natural Language

The phrase "natural language" gets thrown around a lot, but it's worth being specific about what it actually means in practice.

When we say you can build a workflow with natural language, we mean this:

You type: "When a deal is moved to Closed Lost, wait 30 days, then reset the contact's lifecycle stage to Lead, set their lead status to In Progress, and create a high-priority task for the owner saying 'Re-engage this contact  30 days since lost deal.'"

And Claude connected to your HubSpot account via a private API token, translates that description into the exact JSON payload the HubSpot Automation API expects, fires the POST request, and returns a live workflow ID. The workflow is in your HubSpot account, ready to be used.

No schema knowledge required. No clicking through the workflow builder. No risk of misconfiguring a branch or forgetting to set an action. Just a description and a result.

For RevOps teams, this changes the economics of automation. The cost of building a workflow in time, in clicks, and in cognitive load drops dramatically. That means you can build more automations, iterate faster, and spend your energy on the strategy behind the automation rather than the mechanics of building it.

How to Set It Up: The Four Steps

Getting this working requires four one-time setup steps. Once they're done, creating workflows is as simple as describing what you want.

Step 1: Connect HubSpot to Claude

HubSpot has an official connector for Claude that allows Claude to read your CRM data and take actions on contacts, deals, tickets, and more directly from a chat window.

To connect it:

1. In Claude, go to Settings → Connectors → Browse connectors

2. Search for HubSpot in the search bar.

3. Click Connect next to HubSpot and log into your HubSpot account

4. Select your permissions and click Connect app

Once connected, set Write tools to Needs Approval in the connector settings. This ensures Claude always confirms before making CRM changes.

Enable HubSpot in any chat by clicking Search and Tools at the bottom of the chat window and toggling HubSpot on.

Step 2: Create a Legacy App (Your API Token)

HubSpot's Legacy Apps (formerly Private Apps) generate the API token that allows direct workflow creation. This is a one-time setup.

1. In HubSpot, navigate to Development → Legacy Apps

2. Click Create legacy app and give it a clear name (e.g., Claude API Access)

3. Click the Scopes tab and enable the automation scopes and content scopes

4. Click Create app → Continue creating

5. On the Auth tab, click Show token and copy it

Store this token securely; it doesn't expire and acts as a password to your HubSpot account's automation layer.

Step 3: Store Your Credentials in Claude's Custom Instructions

This is the step that makes everything seamless. Instead of pasting your token into every chat, store it once in Claude's Custom Instructions so it's automatically available in every new conversation.

1. In Claude, go to Profile icon → Settings → General

2. In the “Instructions for Claude” field, add:

"My HubSpot Portal ID is [your portal ID]. My HubSpot Legacy App token for workflow creation via the Automation v4 API is [your token]. When I ask you to create a HubSpot workflow, always use this token and portal ID and call the API directly via fetch() in the browser console. Never use the MCP connector or browser UI for workflow creation."

Your Portal ID can be found by looking at your browser's address bar. Your unique Hub ID is the 5- to 8-digit number appearing in the URL, usually formatted as  app.hubspot.com/contacts/{YOUR_PORTAL_ID}. 

With this saved, every future workflow request just needs a plain English description, no credentials, no configuration.

Step 4: Install the Claude in Chrome Extension

The Chrome extension is what allows Claude to execute the API call from your browser, using your authenticated HubSpot session.

1. Install the Claude in Chrome extension from the Chrome Web Store

2. In Chrome's extension settings, set site access to On all sites

3. When you want to create a workflow, make sure you have a HubSpot tab open and the extension active on that tab

That's the full setup. Four steps, done once, and you're ready to build automation with natural language from any Claude chat.

Let's Build Something: A Medium-Complexity Example

To show what this looks like in practice, here's a workflow we built to demonstrate the capability: a New Contact Nurture workflow with behavioral branching.

The Workflow

When a new contact is created in HubSpot with a company name present:

1. Set the contact's lifecycle stage to Lead

2. Wait 5 minutes

3. Send a nurture email

4. Wait 3 days to allow email engagement to be tracked

5. Branch based on behavior:

   • If the contact opened the email, update the lifecycle stage to Marketing Qualified Lead and create a HIGH priority task for the owner: "Follow up with engaged lead within 48 hours"

   • If the contact did not open the email, send a follow-up email and flag the contact as low engagement by setting their lead status to Unqualified

This is a real workflow with genuine branching logic, multiple CRM updates, a task creation, and two email sends across two different paths. In the HubSpot workflow builder, this would take 15–20 minutes to configure carefully. With the natural language approach, here's the prompt that built it:

"Create a HubSpot workflow using the Chrome extension: trigger when a new contact is created with a known company name. Step 1: set the lifecycle stage to Lead. Step 2: delay 5 minutes. Step 3: send our nurture email. Step 4: delay 3 days. Step 5: branch  if the contact opened the email, set lifecycle stage to Marketing Qualified Lead and create a high priority task saying 'Follow up with engaged lead within 48 hours.' If they didn't open it, send our follow-up email and set their lead status to Unqualified."

Claude translated that description into the complete Automation v4 API payload, including the correct action type IDs, enrollment event criteria, LIST_BRANCH structure, and property update syntax  and fired the POST request. The workflow came back with HTTP 201 (created), turned on, and visible in HubSpot within seconds.

The Art of the Possible

What we built here is a starting point, not a ceiling. Now that the workflow creation layer is accessible via natural language, the possibilities scale quickly.

Complex multi-stage sequences built in minutes. Today, it takes a skilled RevOps practitioner upwards of 30 minutes to build a sophisticated nurture sequence with branching, delays, and multiple actions. With this approach, the same sequence takes a single prompt to Claude.

Workflow libraries on demand. Imagine describing ten different workflows, one for each stage of your pipeline, and having all ten built, configured, and turned on in a single conversation. What used to be a week of work becomes an afternoon.

Consistent builds. When humans click through workflow builders, they make mistakes.  A misconfigured branch, a wrong delay unit, a missing action. The API method produces the same output every time based on your description. Your workflows match your prompts.

RevOps that moves at the speed of strategy. The gap between "I want to automate this" and "this is automated" shrinks from days to minutes. That means RevOps can keep pace with sales and marketing strategy in real time, not lagging by a sprint.

Accessible automation for the whole team. Not every RevOps practitioner is comfortable in the workflow builder. With natural language, anyone who can describe a business process can create the automation for it. That's a fundamentally different model for how teams build and maintain their HubSpot instance.

AI-native operations. This isn't just about saving clicks today. It's about building toward a model where your CRM automation layer can be described, generated, reviewed, and deployed conversationally.  A foundation for AI-native revenue operations that teams will build on for years to come.

What We Built  And What It Means

In a single session, we went from concept to a live, active HubSpot workflow built entirely through natural language, without touching the workflow builder once.

We connected HubSpot to Claude, generated an API token through a Legacy App, stored our credentials in Claude's Custom Instructions so they're available in every future conversation, and established a repeatable method that turns a plain English description into a production-ready workflow in under 30 seconds.

The workflow itself covered a real RevOps use case:  a “New Contact Nurture” workflow that automatically set a contact's lifecycle stage upon creation, sent a nurture email, then waited before branching to the next relevant steps. One prompt and a fully branched, multi-step workflow live in HubSpot in seconds, which did not require a single click in the HubSpot workflow builder.

The setup takes less than 30 minutes. After that, building automation is as fast as you can describe it.

We're genuinely excited about where this goes for our team, for our clients, and for the RevOps community broadly, and we want to acknowledge HubSpot for making it possible.

Opening the Automation v4 API to programmatic workflow creation is exactly the kind of platform investment that moves the whole ecosystem forward. It reflects a real commitment to practitioners who want to build on top of HubSpot, not just inside it.

This is one of those capabilities that starts as a neat trick and quietly becomes the way you work. We're already there.

Ready to explore what AI-native RevOps looks like for your team? Let's talk.

About Hyperscayle

Hyperscayle is a revenue operations consulting and implementation firm. We partner with our clients to help them grow and scale, delivering best in class RevOps process and systems that drive revenue from lead to cash. We help companies build and improve their go-to-market operations, combining deep RevOps strategy, systems work, and AI delivery to pair the capabilities of a large consultancy with the responsiveness of a specialized team.

We provide both strategy and execution for your RevOps projects, designing business process and technical solutions, then putting hands on keyboards to implement them in your marketing, sales and finance systems. We’ve solved RevOps challenges across multiple industries, with a focus on SaaS, Manufacturing, Finance and Healthcare.