Outcome. Every time an onboarding ticket's stage or milestone changes, the external project management tool your delivery team actually works in gets updated automatically, so nobody keeps two systems in sync by hand.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-036
flowchart TD
A[Ticket pipeline stage changes, Onboarding pipeline] --> B[Custom code: POST milestone update to project tool]
B --> C{Sync failed?}
C -->|Yes| D[Set status Error, notify integration owner]
C -->|No| E[Set status Synced]
When to use it, when not to
- UseUse it when your implementation or delivery team lives in a project tool (a Kanban or task board) rather than HubSpot, and HubSpot is only the record of truth for the customer relationship.
- UseUse it when the project tool accepts inbound webhooks or has a documented API endpoint for creating or updating a task or card.
- SkipDo not use it as a two-way sync, this fiche only pushes HubSpot changes outward, it does not pull status back from the project tool into HubSpot. A return sync needs a second, tool-specific inbound integration.
- SkipDo not use it if the project tool has an existing native HubSpot integration (several popular ones do), a maintained native connector is usually more reliable than a custom webhook.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.5 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the customer onboarding pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
