Prompt Breeze Assistant or Build the Workflow Manually? Decide Before You Start

You have a lead follow-up sequence in mind.

The question is not whether HubSpot can run it, but how to build it: prompt Breeze Assistant to draft the whole workflow, or assemble each action by hand in the editor.

The right answer depends on what your sequence actually needs, because the two paths have different documented limits.

This article gives you a decision procedure.

You will map your workflow and check its required actions against what Breeze Assistant can and cannot add.

You will also confirm access prerequisites and plan the review step for AI-drafted workflows.

By the end, you should know which build path fits your specific sequence.

Start by mapping the workflow you actually need

Before touching either tool, write down the sequence in plain language.

A typical lead follow-up might enroll contacts who filled out a demo form, wait a set number of days, then send a follow-up email.

It could also create a task for the owner and notify sales if the contact replies.

Then translate that narrative into concrete workflow components.

Every step falls into one of a few categories: an enrollment trigger, an action, a delay, a branch in the logic, or a connection to another system.

Naming each component matters because the two build paths treat these categories differently.

Keep the list short and specific.

'Follow up on new leads' is not a component list.

'Form submission trigger, fixed delay, follow-up email, owner task' is.

The specificity is what lets you check the sequence against the tool's actual scope in the next step.

What Breeze Assistant can build

According to HubSpot's documentation, Breeze Assistant can build complete workflows, including enrollment triggers, actions, delays and more (knowledge.hubspot.com).

In the workflow editor, the picture narrows.

There, Breeze Assistant can only add and edit workflow actions.

It cannot update workflow triggers.

So if you start in the editor and prompt for changes, trigger adjustments stay manual.

If you have Data Hub Professional or Enterprise, note a subscription-specific behavior.

When creating or updating a workflow, if no appropriate actions are identified, a custom code action may be automatically generated with corresponding code.

That is a documented possibility, not a guarantee for every prompt, and it is worth reviewing any generated code carefully before relying on it.

What Breeze Assistant cannot add in the editor

This is the core of the decision.

HubSpot documents a specific list of workflow actions that Breeze Assistant cannot add:

• Go to workflow
• Delay (until an event occurs)
• Format data
• AND/OR logic branch (based on filter criteria)
• Send webhook
• Sending A/B test emails
• Create Salesforce task, Set Salesforce campaign, Add Google Sheets row, and LLM integrations plugged into the Use a custom LLM action

Compare your component list against this exclusion list.

If your sequence depends on any of these actions, those steps need manual configuration regardless of how the workflow started.

A prompt cannot add them in the editor.

Two exclusions deserve special attention for follow-up sequences.

The AND/OR logic branch exclusion means any sequence that routes contacts differently based on combined criteria needs manual branching.

The delay-until-an-event exclusion matters if your follow-up waits for a reply or a meeting rather than a fixed number of days.

Breeze Assistant can build workflows including delays generally, so a simple fixed delay is not automatically a problem.

The specific 'until an event occurs' delay type is what the exclusion names.

Confirm the prerequisites before committing to a path

Breeze Assistant is not available on every plan or to every user.

Availability covers Marketing, Sales, Service, Data, Smart CRM, and Revenue Hub Professional or Enterprise, except where noted (knowledge.hubspot.com).

Check which hub your workflow lives in and whether that hub's tier is on the list.

Permissions and settings add two more conditions.

Super Admin or Workflows permissions are required to use the workflows tool.

To use Breeze Assistant with your workflow, the 'Give users access to generative AI tools and features' and 'Give users access to Breeze Assistant' settings must be turned on.

HubSpot also recommends turning on the CRM data settings so outputs are relevant to your company.

You can manage AI feature access in your AI settings and configure what data is shared.

HubSpot points to its AI Trust FAQs and AI Model Cards for details on security, data use and compliance.

If any of these conditions is missing, resolve them first.

The documentation does not state that manual building is a fallback when permissions or a qualifying subscription are absent.

Verify your own access before assuming either path is open.

Plan for the review gate

Here is the step that changes how the prompt path feels in practice: by default, workflows created by Breeze Assistant are turned off.

You will need to review the workflow and manually turn it on (knowledge.hubspot.com).

That means prompting does not produce a live workflow.

It produces a draft that a person must inspect and activate.

Treat that review as part of the build, not an afterthought.

Check the enrollment trigger against your intent, read each action's settings, and confirm delays and branches match the sequence you mapped.

This review gate is also where the two paths converge.

A manually built workflow also needs review before activation.

The difference is that with a prompt-built workflow, you are reviewing someone else's first draft rather than your own assembly.

Would you find it easier to critique a draft you did not build, or to assemble each step deliberately yourself?

Both are legitimate, and the review requirement applies either way.

An illustrative comparison

Consider two follow-up sequences to see the decision in action.

These are illustrative scenarios, not customer results.

Sequence A: enroll contacts who submitted a demo request form, wait a fixed delay, send a follow-up email, then create a task for the contact owner.

Every component here is either a trigger, a standard action, or a delay that Breeze Assistant can include when creating a complete workflow.

None of the required actions appears on the exclusion list.

This sequence is a candidate for the prompt path: describe it, review the draft, and activate manually.

Sequence B: enroll the same contacts, but branch the flow so contacts matching combined criteria get a different path.

It also sends an internal webhook to another system when a high-intent reply arrives.

Both the AND/OR logic branch and the Send webhook actions are on the exclusion list.

Even if Breeze Assistant drafts the enrollment trigger and the email actions, those two steps must be built manually in the editor.

Here the practical answer is a hybrid: prompt for what it can add, then configure the excluded actions by hand.

The lesson generalizes: the prompt path is viable when your sequence stays within the documented scope.

Partial or fully manual work is required as soon as an excluded action appears.

The exclusion list, not prompt quality, is the deciding factor.

Building manually: a note on placeholders

If you choose the manual path, HubSpot's placeholder feature can change how you sequence the work.

Most workflow actions, such as Create task and Send email, can be saved without setting all of the details (knowledge.hubspot.com).

You can add actions first as placeholders, then fill in the details later before turning the workflow on.

Two conditions apply.

Placeholder actions can only be added to inactive workflows; you cannot add a placeholder when a workflow is turned on.

Some actions cannot be saved as placeholders at all: custom code, Format data, and both delay types.

Actions from connected apps must also be fully set up before you continue building.

For a follow-up sequence where the emails are not written yet, placeholders let you structure the whole flow first and drop in the finished emails afterward.

Use the Review button in the editor to see all incomplete placeholder actions before activation.

If your sequence relies heavily on delay actions or connected-app actions, the placeholder benefit shrinks, since those must be fully configured up front.

The decision, summarized

Work through four checks in order:

1. Map the sequence. List the trigger, every action, every delay and every branch in plain language.
2. Check the exclusion list. If any required action is one Breeze Assistant cannot add in the editor, plan to build that step manually.
3. Confirm access. Verify the subscription tier for the relevant hub, the Super Admin or Workflows permission, and the generative AI and Breeze Assistant settings.
4. Plan the review. Whichever path you choose, the workflow needs human review before it goes live; Breeze-created workflows are off by default until you turn them on.

If all four checks pass cleanly, prompting Breeze Assistant to draft the complete workflow is a reasonable starting point, with the editor available for refinements.

If the exclusion list catches any required step, start with whichever path covers more of your sequence and finish the rest manually.

If access settings are unresolved, settle those first, because neither path works without them.

One caution applies to either path: the documentation describes what each tool can add and edit, not how well any particular prompt or manual build will perform once live.

Your review step is where quality gets checked, so budget attention for it rather than treating activation as a formality.

Related decisions before you build

A few neighboring choices shape the build as much as the tool does.

If you are still settling on the trigger itself, see when to manually enroll contacts instead of fixing the trigger.

If the workflow should wait on a calendar rather than an event, deciding whether a workflow should run on a schedule covers that timing question.

And if you are weighing whether to start from a template, the template-versus-build-from-scratch decision pairs naturally with the prompt-versus-manual choice here.

For the object the workflow should act on, choosing the workflow object type is worth settling before either build path begins.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.