A HubSpot workflow watches for a trigger, a property changing, a form submitting, a deal moving stage, then runs a set of actions: send an email, update a field, create a task, wait, branch, or call out to another system. It's genuinely powerful for anything the trigger and the action both live inside HubSpot's own data. The honest limits show up the moment either side of that doesn't.
Workflows run portal-wide and start automatically: a contact fills out a form, a deal's stage changes, a property crosses a threshold, and the workflow enrolls the matching record without anyone clicking anything. From there it's a sequence of actions, send an internal notification, delay three days, branch on whether a field is set, rotate a lead to the next rep, with no cap on how long or complex the chain gets.
This is different from a sequence, which is a sales rep's personal, manually-enrolled email-and-task cadence aimed at one contact at a time, and which pauses the moment that contact replies. Workflows are the broader, automatic, portal-wide tool; sequences are the narrower, manual, one-to-one one. Real search volume mixes the two up constantly, which is fair, since on the surface they look similar.
Two of the only actions that let a workflow reach outside HubSpot, a webhook call to an external URL and a custom code step, are gated behind paid tiers (Professional and up for webhooks, Operations Hub for custom code). Without those, a native workflow can really only touch HubSpot's own properties and a short list of App Marketplace integrations. That's not a bug; it's just where the free and lower tiers draw the line.
The bigger limit, and one most people never run into because they never try: there's no API to actually build or edit a workflow's logic. HubSpot's Workflows API lets you enroll or unenroll a record and read a workflow's metadata, but the steps themselves, the triggers, the branches, the actions, only get built by a person clicking through the UI, one workflow, in one portal, at a time. If you need the same automation replicated across many portals, or rebuilt after a template change, there's no official shortcut.
And a workflow only ever knows what's already a HubSpot property. It can't react to something happening in your ERP or your warehouse in real time, only to the moment that fact gets synced onto a record it's watching.
Instead of paying up a tier for a native webhook step, we build the listener that watches for the same property change and reaches out to the external system directly, filling the exact gap the lower tier leaves open.
Since there's no API for a workflow's actual logic, cloning or updating the same automation across dozens of portals is a UI-only job. We do that through browser automation, which can do in minutes what the UI forces a person to do one portal at a time.
If the action needs to happen outside HubSpot, or the trigger lives outside it, that's exactly the gap we build across.
Tell us what the workflow would do if it could reach outside HubSpot, or what it would take to build the same automation across every portal you run. We build both directions: filling the gap inside HubSpot regardless of which tier you're on, and connecting it to whatever system sits outside it. Workflows are one example; n-frames automates whatever's manual, anywhere in your business.
Let's talk →A workflow is automatic and portal-wide: it enrolls whatever matches its trigger, no person required, and can touch contacts, deals, tickets, or companies. A sequence is a sales rep's own manually-enrolled, one-to-one outreach cadence for a single contact, and it stops the moment that contact replies. Workflows automate the business; sequences automate a rep's own follow-up.
Yes, through the webhook action or a custom code action, both gated to paid tiers (Professional and up, or Operations Hub for custom code). Below those tiers, a native workflow has no built-in way to reach an external API directly.
Only partially. The Workflows API can enroll or unenroll specific records and read workflow metadata, but it can't create or edit the workflow's actual logic, the triggers and action steps. Building the logic itself is UI-only, no official API path around it.
By default, a workflow only enrolls records going forward from the moment it's turned on; it doesn't retroactively act on contacts who already matched the trigger beforehand. Turning on re-enrollment, or running the workflow once against a static list of the existing records, is how most people catch that gap.
Lead rotation to the next available rep, an internal Slack or email alert when a high-value deal stalls in one stage too long, a nurture sequence of emails triggered by a form fill, and automatically updating a lifecycle stage property when a deal closes. All of them follow the same shape: a trigger inside HubSpot, then a chain of actions inside it too.