New · 31 AugSimulate a record before it existsRead the release notes

See what your HubSpot workflows do to a new record

Describe a record, or fill in one of your own forms, and Entflow runs it against every active workflow in your portal. You see which workflows pick it up, in what order, what each step changes, and which workflows didn't fire and why. It works from your synced workflows, so nothing touches HubSpot.

Connect HubSpot · FreeSee pricing
Rated 5.0 out of 5 on the HubSpot Marketplace · 3 reviews
  • Two writes, one instant Two workflows set Lifecycle stage on creation. Both are flagged Race, because HubSpot doesn't say which lands last.
  • One change sets off another Setting Marketing Qualified Lead enrolls the Welcome series, drawn as a dashed cascade link.
  • Delays in real time The Welcome series' Wait 2 days holds it; its two emails land in the 2 days later column, just right of this view.

Which workflows pick it up, and when

Pick an object, set the properties that matter and a creation time, and Simulate works through your active workflows. The canvas lays the run out left to right: one column for each moment something happens, one row for each enrollment, with the real elapsed time on every column. Waits are read from your workflows' own delays, so a two-day delay lands two days later.

  • A contact, company, deal or any other object
  • Or submit one of your own forms, hidden fields included
  • Delays measured from the creation time you choose
  • Canvas for the shape of the run, Story to read it in order

Follow the chain from one workflow to the next

When one workflow sets the field that enrolls the next, the canvas draws that link and starts the second workflow at the moment of the change. Every property a step writes re-checks every workflow's enrollment criteria, so a chain several workflows deep shows up on the canvas, and each step can tell you why its workflow ran.

  • Cascades drawn as links between workflows
  • Enrollment re-checked on every property write
  • Two workflows writing the same property in the same instant are flagged as a Race
  • Races are flagged, not settled: HubSpot doesn't guarantee which write lands last

An answer to "why didn't this fire?"

Every workflow that did not enroll is listed with the one condition that blocked it, so a workflow that stayed quiet has an answer instead of a hunt. After the run, Simulate compares the record as you described it with the record once every workflow has run, property by property.

  • The blocking condition for each workflow that didn't enroll
  • Each property that ends up different, and when it changed
  • Why each workflow ran, and why each branch went the way it did

Honest about what it can't know

Times come from the delays configured in your workflows. HubSpot's own enrollment and processing latency isn't included, so real runs land slightly later than shown. Anything the simulation cannot know, such as custom code, webhooks, a wait on a real-world event like an email open or a page view, or two workflows writing the same property at once, is marked rather than guessed.

  • Custom code and webhooks marked as an unknown effect
  • Waits on real-world events marked as unreachable
  • Runs on your synced, active workflows: no HubSpot calls, no writes
  • Starter plans see the first few workflows and one cascade step; Growth and above see the full run

More ways Entflow helps you stay on top of your HubSpot workflows.

See what a new record sets off

Connect HubSpot and simulate a record against your own workflows. Every account starts with a 14-day Pro trial.

Connect HubSpot · FreeSee pricing

No credit card · 14-day Pro trial