Launch a Wrike onboarding project when a HubSpot deal closes won

The second a deal flips to closed won, spin up the right Wrike onboarding project from a blueprint, fill it with deal context, and post the kickoff in Slack.

Agentic Task
HubSpotWrikeSlack BotSalesOperationsOnboarding AutomationNotifications & Alerts

Build me an agent workflow that kicks off a Wrike onboarding project every time a HubSpot deal moves to closed won.

Trigger: a HubSpot webhook for deal stage changes. When the deal stage updates to closed won (or a stage I configure), run the workflow. Use the deal ID from the webhook payload as the input to the rest of the run.

Step 1: Fetch the full deal from HubSpot using Get Deal. Include the standard deal properties (deal name, amount, close date, deal stage, pipeline, deal type, product line if present, owner / account exec, notes / description) and pull the associated primary company and primary contact (name and email).

Step 2: List Wrike folder blueprints with List Folder Blueprints. Pick the blueprint whose title best matches the deal's product line or deal type. If nothing is a confident match, fall back to a default onboarding blueprint that I configure during setup, and remember that a fallback was used so we can flag it later.

Step 3: Launch that blueprint with Launch Folder Blueprint Async under a configurable Wrike parent folder (the customer onboarding folder). Name the new project after the associated company on the deal. The launch is async, so poll the async job until it completes and capture the new folder / project ID and permalink.

Step 4: Drop a kickoff context block onto the new Wrike project using Create Folder Comment. The comment should include deal amount, close date, account exec / deal owner, primary contact name and email, company name, and the deal notes / description, formatted as a clear structured block that the services lead can scan.

Step 5: Post an announcement in a configurable Slack channel (the services team channel) using Slack Bot Send a Message. The message should announce the new customer, name the AE, link to the new Wrike project via the permalink, and call out which blueprint was used. If the fallback blueprint was used because no good match was found, prefix or tag the message so the services lead knows to verify the template choice.

Configurables I want to expose: the HubSpot pipeline / closed-won stage to watch, the deal property used to pick a blueprint (product line vs deal type vs custom), the mapping from that property's values to specific Wrike blueprint titles, the default fallback blueprint, the Wrike parent folder for new customer projects, the Slack channel for announcements, and which deal fields go into the kickoff comment.

If the deal is missing a primary contact or company, still launch the project but flag the missing fields in both the kickoff comment and the Slack message so the services team can fill them in.

Additional information

What does this prompt do?
  • Watches HubSpot for deals that move into the closed won stage, so the services team never has to remember to start onboarding by hand.
  • Picks the right Wrike onboarding project template based on the deal's product line or deal type, and falls back to a default template when nothing matches.
  • Creates the new project under your customer onboarding folder, names it after the account, and posts a structured kickoff note with deal amount, close date, account exec, primary contact, and deal notes.
  • Announces the new project in your services team Slack channel with a direct link, and flags it when a fallback template was used so a human can adjust.
What do I need to use this?
  • A HubSpot account where deals flow through a pipeline with a closed won stage.
  • A Wrike workspace with at least one onboarding project template saved as a folder blueprint, plus a parent folder to hold new customer projects.
  • A Slack workspace and the channel where your services or customer success team wants kickoff announcements posted.
How can I customize it?
  • Change which deal property decides the template (product line, deal type, region, ARR band) and map each value to a specific Wrike blueprint.
  • Pick which fields go into the kickoff note posted on the new project, like deal amount, close date, account exec, primary contact, and deal notes.
  • Swap the Slack channel, tweak the announcement copy, or route announcements to a different channel when the fallback template is used.

Frequently asked questions

Do I need to keep the Wrike templates updated for this to work?
Yes. The workflow looks at the folder blueprints saved in your Wrike workspace, so any change you make to those templates is reflected the next time a deal closes. You do not have to redeploy anything.
What happens if no template matches the deal?
The workflow falls back to a default onboarding template that you choose during setup, and the Slack announcement flags that a fallback was used so the services lead can verify or rework the project.
Can I change which Slack channel gets the kickoff message?
Yes. The channel is a setting on the workflow, so you can point it at your services team channel, a dedicated customer onboarding channel, or a DM to the customer success lead.
Will this work with custom deal properties in HubSpot?
Yes. You can point the template picker at any deal property, including custom ones like product line, ARR band, or region, and the kickoff note can pull in any fields you want surfaced for the team.
Does the new Wrike project get named after the customer?
Yes. The workflow names the project after the associated company on the deal so it shows up clearly in your customer onboarding folder.

Stop manually spinning up onboarding projects after every deal.

Connect HubSpot, Wrike, and Slack once, and every closed-won deal kicks off the right onboarding project with a full context note for the services team.