Build it once.
Ship it to every portal you run.
You got lead routing right for one client. Right now it is trapped in their portal, and the next client starts from a blank workflow. The Vault lifts a workflow out of one portal and puts it into the others, properties and all, switched off so you review it first.
Sandbox to productionOne client to the nextFree for the whole beta
Your best automation is stuck where you built it.
You start from a blank canvas
Two days getting routing, SLA timers and lifecycle right. The next client wants the same thing and none of it comes with you. You type it out again.
Today: the same work, at a discount you did not intend to give.
Sandbox to production, by hand
You test properly, then rebuild the tested thing in production clicking through the same screens, hoping you match it exactly.
Today: the rebuild is where the bugs come from.
The fix lands in one portal
You improve the routing for one client. The other eleven keep the old version, because rolling it out means eleven manual edits nobody has budget for.
Today: your portfolio drifts apart.
A workflow becomes something you can send.
Lift it out of any portal
Connect read-only, pick the workflow. It comes out with its actions, its branches and the properties it depends on.
Drop it into as many as you like
Tick the portals. Missing properties are created first, then the workflow itself, switched off in each one.
Told in advance what will not fit
A workflow points at owners, teams and lists that live in one portal only. You see which ones need a choice before anything is written, not after.
Roll an improvement across the portfolio
Fix it once in the portal where you noticed, then push the same version everywhere else that runs it.
Why this one will actually ship
The half that writes a workflow into a portal is live. It is what installs the library's specs today.
We pulled 60 workflows straight out of a live portal on 26 September. Every one came back in full.
We have documented 515 HubSpot workflows down to the action. We know what a workflow is made of.
Bring your whole portfolio into the beta.
- Free for the whole beta, every portal you connect.
- The founding price after, locked for as long as you keep it.
- Your awkward portals get fixed first. The transfers we make work are the ones on this list.
- Two emails, ever. One when the round trip is measured, one when it opens.
We are taking 20 portals into the beta, because each one gets tested by hand before we let it near production.
Join the founding list
Ten seconds. No card, no call.
We use the answer to decide what to test first. Nothing else, and you can leave the list in one click.
We write when the round trip is measured, and again when it opens. Nothing in between.
There is a second half to this. The same copies are dated, so you can also put a workflow back to the version that still worked. The portal-to-portal side
Before you sign up: the one thing we have not proved yet
Reading a portal is measured. Writing into a portal is live. What we have not done yet is run one workflow all the way round, out of one portal and into another, and compare it action by action against the original. Until we have that number we are not selling this, which is why the list is free and why there is no card on this page.
Two more things worth knowing. Our read test ran on a developer test account, where HubSpot opens features regardless of plan, so on a real portal expect this to need Marketing Hub Professional or above. And a workflow points at owners, teams and lists that exist only in the portal it came from, so a copy always needs those resolving at the other end.
If the round trip turns out to lose too much, we publish the number here and close the list rather than ship something that quietly does less than you think.