Workflow library
Ready-made HubSpot workflows that fire on Sillage intent — installed switched off, for you to review.
Pushing intent into HubSpot is only half the job. The other half is making something happen when it lands: a task for the owner, a Slack ping, an internal email.
The workflow library builds those HubSpot workflows for you. Open it from the Workflow Library button on the HubSpot card in Settings → Integrations.
Every workflow is installed switched off. Sillage creates it in your portal, you review the triggers in the HubSpot editor, and you decide when to turn it on. Nothing starts firing behind your back.
What's in the library
| Workflow | Fires when | What it does |
|---|---|---|
| New Sillage lead → Task | A lead tracked by Sillage lands in HubSpot | Creates a follow-up task for the record owner |
| New intent detected → Task | Sillage detects a new signal on a contact | Creates a task for the owner, with the signal and score in the body |
| Hot intent (score ≥ 80) → High-priority task | A contact reaches an intent score of 80 or more | Same, at high priority |
| New intent → Slack notification | Sillage detects a new signal | Posts a Slack message |
| New intent → Email to owner | Sillage detects a new signal | Sends an internal email to the record owner |
The four intent workflows re-enrol the contact every time a new signal is detected, so a contact that goes quiet and then moves again triggers again. The "New Sillage lead" one fires once, when the contact first appears.
Tasks and emails go to the HubSpot record owner, so whoever owns the account gets the nudge. The Slack one posts to a channel you pick.
Installing one
Click Install
Admins only. Sillage creates the workflow in your portal under the name 🟣 Sillage — … (template).
Review it in HubSpot
The card now shows Installed · Off and an Open in HubSpot link. Open it, read the enrolment criteria and the action, and change anything you want — it is a normal HubSpot workflow from that point on, yours to edit.
Turn it on
Enable it in HubSpot. The card in Sillage then shows Installed · On.
Installing the same template twice does nothing — Sillage recognises a workflow of that name already exists in your portal and leaves it alone. So if you edited it, your edits are safe.
Two things that need setting up
The Slack workflow needs a channel. HubSpot won't let Sillage pick it, so after installing, open the workflow in HubSpot and choose the destination channel. It also requires HubSpot's own Slack integration to be connected in your portal.
Workflows need HubSpot Pro or above. They are not part of Starter. If your portal is below Pro, Sillage tells you when you try to install rather than failing silently.
"Reconnect HubSpot to enable workflows"
If you see this banner, your HubSpot connection was made before Sillage supported workflows, so it was never granted permission to create them.
Click Reconnect HubSpot (admins only). It re-runs the same authorisation and re-grants the permissions — your existing connection, settings and synced data are untouched. Then install the workflow again.
Building your own instead
Nothing forces you to use these. Every Sillage property is a normal HubSpot property, so you can build any workflow, list or view you like on top of them — see what Sillage writes. The library is just a fast start for the four or five automations most teams end up building anyway.