HubSpot closed-won to Asana: a fast handoff with the right customer data

A good sales-to-onboarding handoff does three things: it starts the moment the deal closes, it carries the customer's data exactly as it is in the CRM, and it keeps the CRM and other systems up to date as onboarding progresses. Done by hand, each of those depends on a person and strong cross-functional coordination. Someone has to notice the win, copy the deal details, and report progress back to sales and other teams that need it.

The flow has seven native steps and no code.

1. 1
   HubSpot calls the flow's webhook whenever a deal changes stage.
2. 2
   A filter lets only Closed Won through.
3. 3
   A Build text step reads the deal ID from HubSpot's message.
4. 4
   Get Deal reads the deal and its associated company.
5. 5
   Get Company returns the customer's name, "The Empire".
6. 6
   A second Build text step names the project "Onboard: The Empire".
7. 7
   Asana duplicates the customer success team's onboarding template under that name.

In Asana, the new project has all four sections (Kickoff, Setup, Training, and Go-live) and all nine tasks from the template.

The webhook is what makes it fast. HubSpot calls the flow the moment the stage changes, so nothing waits for a scheduled check.

The data is right because nobody types it. HubSpot's message carries the deal ID and its new stage, not the customer's data, and the flow reads the company name from the company record. The same goes for any other field you need at kickoff, such as the deal amount, product entitlement, support tier, or the account owner.

I also ran the unchanged flow on an On-Prem Worker, our runtime installed inside your network, in a Docker container and on a Mac. Both runs took about three seconds, nearly all of it Asana copying the template. HubSpot's webhook message came in through the Neblex cloud, which hosts the webhook; everything the flow read and wrote after that stayed on the On-Prem Worker, and the Neblex cloud kept only the run's status, diagnostics, counts and integrity receipts.

That copy is the heavy part. Asana runs project duplication as a job that finishes in the background, and allows each user only five such jobs at a time, including any started in the Asana app, so a flow that handles a burst of won deals at quarter end should space out the copies.

The demo goes one way. The handoff is complete when onboarding progress shows up where sales and account managers already work, and that takes a second flow in the other direction, which isn't in this demo:

• the Asana project link on the HubSpot deal, which also stops a deal from getting two projects
• onboarding status on the company record
• the go-live date, for HubSpot and for billing or support

If onboarding starts when someone notices a won deal, the start date depends on that person. Agree on which stage starts onboarding and who owns the template; the flow is a quick build. If you want to see it with your own pipeline, ask for a demo.

• Duplicate a project, Asana Developers
• Rate limits, Asana Developers (duplication, template and export jobs: 5 at a time per user, including jobs started in the Asana app)
• Demo flow and run: built in Neblex and recorded on October 28, 2026, with a test HubSpot portal and an Asana workspace set up for demos.

Last checked: October 30, 2026.