The Workflow Library

Library / Customer onboarding / customer-onboarding-040

Slack channel request automation via webhook

Customer onboardingDealData Hub ProfessionalAdvanced~60 min to buildFull spec

Outcome. A closed-won deal automatically gets a dedicated Slack channel created and shared with the deal owner and onboarding owner, instead of someone remembering to set one up by hand.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-040
flowchart TD
    A[Deal stage = Closed Won, no Slack channel yet] --> B[Custom code: create Slack channel, invite owners, post message]
    B --> C{Creation failed?}
    C -->|Yes| D[Notify integration owner of failure]
    C -->|No| E[Set Slack Channel URL on deal]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when your team runs onboarding conversations in per-customer Slack channels and channel creation is currently a manual, easy-to-forget step.
  • UseUse it when a Slack app with the conversations.create and conversations.invite scopes can be installed in your workspace, this needs Slack admin cooperation once, not per deal.
  • SkipDo not use it expecting the native HubSpot-Slack integration to create channels on its own, that integration posts notifications and messages, it does not create or manage channels, this fiche calls the Slack Web API directly instead.
  • SkipDo not use it for every deal if channel sprawl is already a problem in your workspace, add an amount or plan-tier filter to the enrollment criteria first.
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.4 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.