From hubspot-admin
Build workflows to automate contact progression through the sales funnel: Lead to MQL to SQL to Opportunity to Customer. Each transition is triggered by a specific event (score threshold, meeting booked, deal created, deal won).
npx claudepluginhub tomgranot/hubspot-admin-skillsThis skill uses the workspace's default tool permissions.
Automate the contact journey through the sales funnel with four progression workflows, each triggered by a specific business event.
Build a HubSpot workflow that auto-enriches and stages new contacts upon creation. Sets lifecycle stage, copies company name and industry from associated company, and branches on completeness. Must be built manually in the HubSpot UI due to API limitations.
Designs revenue operations for lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use for marketing, sales, customer success workflow alignment.
Optimizes revenue operations for lead lifecycle, scoring, routing, MQL/SQL qualification, pipeline management, and marketing-to-sales handoffs.
Share bugs, ideas, or general feedback.
Automate the contact journey through the sales funnel with four progression workflows, each triggered by a specific business event.
| From | To | Trigger |
|---|---|---|
| Lead | MQL | Lead score exceeds threshold |
| MQL | SQL | Meeting booked |
| SQL | Opportunity | Deal created and associated |
| Opportunity | Customer | Deal marked as closed-won |
/build-lead-scoring first)Follow the step-by-step instructions in the "Execute" section below. This is the most reliable method and gives you full control over every trigger, branch, and action.
HubSpot's built-in Breeze AI can generate workflow skeletons from natural language prompts. Navigate to Automation > Workflows > Create workflow > "Describe what you want" and paste one prompt per workflow. You will need to create four separate workflows:
Workflow 1 -- Lead to MQL:
Create a contact-based workflow that triggers when a contact's HubSpot score
is greater than or equal to [your MQL threshold] AND their lifecycle stage is "Lead".
The workflow should set the lifecycle stage to "Marketing Qualified Lead"
and send an internal notification to the marketing team.
Workflow 2 -- MQL to SQL:
Create a contact-based workflow that triggers when a meeting is booked with
a contact AND their lifecycle stage is "Marketing Qualified Lead".
The workflow should set the lifecycle stage to "Sales Qualified Lead"
and send an internal notification to the sales owner.
Workflow 3 -- SQL to Opportunity:
Create a contact-based workflow that triggers when a contact has an associated
deal created AND their lifecycle stage is "Sales Qualified Lead".
The workflow should set the lifecycle stage to "Opportunity".
Workflow 4 -- Opportunity to Customer:
Create a contact-based workflow that triggers when a contact's associated deal
stage equals "Closed Won" AND their lifecycle stage is "Opportunity".
The workflow should set the lifecycle stage to "Customer"
and send an internal notification to the CS/onboarding team.
CRITICAL WARNING: Breeze trigger limitations. Breeze creates event-based triggers (OR logic) instead of filter-based triggers (AND logic). Each of these four workflows requires AND logic between the event condition and the current lifecycle stage. After Breeze creates each workflow, you MUST manually verify and fix the trigger/enrollment conditions in the UI to ensure both conditions are ANDed together. Breeze is best used for creating the workflow skeleton (actions, branches, delays) -- the trigger conditions almost always need manual correction.
Additional Breeze limitations for these workflows:
The Claude Anthropic Chrome extension lets Claude see and interact with the HubSpot workflow builder UI directly. You can describe the workflow logic in natural language and Claude will click through the UI to build it. This is often more accurate than Breeze for workflows requiring precise AND-logic triggers, because Claude can verify each trigger condition visually.
To use this approach:
Note on Fast Mode: If you're using Claude Code's Fast Mode to speed up workflow creation, be aware of the billing model: Haiku usage is included in your subscription, but Opus in Fast Mode consumes extra credits. For workflow building tasks (which are UI-heavy and may require many interactions), consider whether the speed tradeoff is worth the credit cost.
Build each as a separate contact-based workflow.