Hubspot sequences skill

Designs and optimizes HubSpot sequences: enrollment triggers, multi-channel steps, task creation, analytics, and A/B tests.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# HubSpot Sequences

## Overview
HubSpot Sequences power the SDR and AE outbound motion inside Sales Hub.
Done right, they automate touches while maintaining personalization. Done wrong,
they're spam cannons that burn your domain reputation.

## Authoritative Foundations
- **HubSpot Knowledge Base — Sequences** — Configure enrollment, task steps, and automatic unenrollment on reply or meeting booked; sequenc…
- **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and res…
- **Outreach — Sales Engagement Cadence Design** — Sequence governance, task-based selling, and CRM-locked cadences.

## When to Use
- "Set up HubSpot sequences"
- "Build HubSpot cadences"
- "Optimize HubSpot sequence performance"

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Hubspot sequences

LeadMagic/main1 file shown
SKILL.md
Show the full text145 lines

HubSpot Sequences

Overview

HubSpot Sequences power the SDR and AE outbound motion inside Sales Hub. Done right, they automate touches while maintaining personalization. Done wrong, they're spam cannons that burn your domain reputation.

Authoritative Foundations

  • HubSpot Knowledge Base — Sequences — Configure enrollment, task steps, and automatic unenrollment on reply or meeting booked; sequences send from each rep's connected inbox.
  • Google and Yahoo — Bulk sender requirements (2024) — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-inbox daily volume.
  • Outreach — Sales Engagement Cadence Design — Sequence governance, task-based selling, and CRM-locked cadences.

When to Use

  • "Set up HubSpot sequences"
  • "Build HubSpot cadences"
  • "Optimize HubSpot sequence performance"
  • "HubSpot sequence A/B test"

Step-by-Step Process

Phase 1: Sequence Architecture

Design sequences by persona and trigger:

  • Inbound follow-up: Auto-enroll on form fill, 3-touch, 7-day window
  • Outbound cold: Manual enroll after list build, 6-touch, 21-day window
  • Re-engagement: Enroll on CRM status change, 3-touch, 14-day window
  • Event follow-up: Enroll on event attendance, 2-touch, 5-day window
Phase 2: Step Configuration

Per step: channel, timing, template, task creation rules.

  • Email steps: plain text, from first name, no tracking pixel if cold
  • Call steps: auto-create task with call notes template
  • LinkedIn steps: manual task (HubSpot can't automate LinkedIn)
  • Delay steps: minimum 2 business days between touches
Phase 3: Enrollment Rules
  • Suppression: don't enroll if already in another sequence
  • Unenrollment: auto-unenroll on reply, meeting booked, or bounce
  • Queue limits: max 50 contacts per sender per sequence
  • Business hours: only send Mon-Thu 6am-8pm prospect timezone
Phase 4: A/B Testing

Test one variable at a time with 2-week minimum run time:

  • Subject lines (2-3 variants)
  • Opening lines (different hooks)
  • CTA phrasing (soft vs direct)
  • Send time (morning vs afternoon)
Phase 5: Analytics

Track: enrollment rate, completion rate, reply rate, meeting rate. Kill sequences with <1% reply rate after 50+ enrollments.

Output Format

Sequence design document with: architecture map, step-by-step configuration, enrollment/unescape rules, A/B test plan, and analytics dashboard design.

Quality Check

Before delivering, verify:

  • All required sections are complete
  • Output matches the user's stated need
  • Named frameworks are cited for key recommendations
  • No vague claims — every recommendation has a specific action
  • Deliverable is ready for operational use, not just conceptual

Common Pitfalls

  1. Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
  2. Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
  3. Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.

Execution Artifacts

  • references/framework-notes.md — HubSpot workflow enrollment, rep-triggered rules
  • templates/output-template.md — properties + workflow + sequence deliverable
  • scripts/check-output.py — local checklist validator This skill includes lightweight artifacts the agent can load on demand:
  • references/enrichment-enrollment-gate.md — lm_email_status workflow gate
  • references/pat-spielmann-outbound-copy.md — verify-before-enroll (Pat Spielmann)
  • references/gtm-table-blueprints.md — clay-toolkit property map
  • references/leadmagic-waterfall.md — loop list → workflow pattern
  • references/gtm-experts-outbound-index.md — expert router Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions
  1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
  2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
  3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
  4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
  5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

  • HubSpot Sequences Best Practices: apply only the part that directly improves the requested deliverable.
  • ColdIQ Multi-Channel Cadence: apply only the part that directly improves the requested deliverable.
  • Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
Deliverable Standard

A strong output from this skill includes:

  • A crisp diagnosis of the current situation
  • A recommended path with tradeoffs, not a generic list
  • A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
  • A measurement plan with leading and lagging indicators
  • Risks and edge cases called out before execution
Adaptation Rules
  • For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
  • For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
  • For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
  • cold-email-strategy, cold-email-copywriting, sending-platforms, inbox-setup, email-deliverability
1---
2name: hubspot-sequences
3description: >-
4 Designs and optimizes HubSpot sequences: enrollment triggers, multi-channel
5 steps, task creation, analytics, and A/B tests. Use when the user is building
6 or fixing sequences in HubSpot Sales Hub. Triggers on: "HubSpot sequences",
7 "HubSpot automation", "HubSpot cadence", "sales hub sequences".
8license: MIT
9compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
10metadata:
11 version: "1.0.0"
12 author: LeadMagic
13 category: tools
14 tags: [hubspot, sequences, sales-hub, crm, cadence]
15 frameworks:
16 - "HubSpot Knowledge Base — Sequences"
17 - "Google and Yahoo — Bulk sender requirements (2024)"
18 - "Outreach — Sales Engagement Cadence Design"
19---
20 
21# HubSpot Sequences
22 
23## Overview
24HubSpot Sequences power the SDR and AE outbound motion inside Sales Hub.
25Done right, they automate touches while maintaining personalization. Done wrong,
26they're spam cannons that burn your domain reputation.
27 
28## Authoritative Foundations
29- **HubSpot Knowledge Base — Sequences** — Configure enrollment, task steps, and automatic unenrollment on reply or meeting booked; sequences send from each rep's connected inbox.
30- **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-inbox daily volume.
31- **Outreach — Sales Engagement Cadence Design** — Sequence governance, task-based selling, and CRM-locked cadences.
32 
33## When to Use
34- "Set up HubSpot sequences"
35- "Build HubSpot cadences"
36- "Optimize HubSpot sequence performance"
37- "HubSpot sequence A/B test"
38 
39## Step-by-Step Process
40 
41### Phase 1: Sequence Architecture
42Design sequences by persona and trigger:
43- **Inbound follow-up:** Auto-enroll on form fill, 3-touch, 7-day window
44- **Outbound cold:** Manual enroll after list build, 6-touch, 21-day window
45- **Re-engagement:** Enroll on CRM status change, 3-touch, 14-day window
46- **Event follow-up:** Enroll on event attendance, 2-touch, 5-day window
47 
48### Phase 2: Step Configuration
49Per step: channel, timing, template, task creation rules.
50- Email steps: plain text, from first name, no tracking pixel if cold
51- Call steps: auto-create task with call notes template
52- LinkedIn steps: manual task (HubSpot can't automate LinkedIn)
53- Delay steps: minimum 2 business days between touches
54 
55### Phase 3: Enrollment Rules
56- Suppression: don't enroll if already in another sequence
57- Unenrollment: auto-unenroll on reply, meeting booked, or bounce
58- Queue limits: max 50 contacts per sender per sequence
59- Business hours: only send Mon-Thu 6am-8pm prospect timezone
60 
61### Phase 4: A/B Testing
62Test one variable at a time with 2-week minimum run time:
63- Subject lines (2-3 variants)
64- Opening lines (different hooks)
65- CTA phrasing (soft vs direct)
66- Send time (morning vs afternoon)
67 
68### Phase 5: Analytics
69Track: enrollment rate, completion rate, reply rate, meeting rate.
70Kill sequences with <1% reply rate after 50+ enrollments.
71 
72## Output Format
73Sequence design document with: architecture map, step-by-step configuration,
74enrollment/unescape rules, A/B test plan, and analytics dashboard design.
75 
76 
77 
78## Quality Check
79 
80Before delivering, verify:
81- [ ] All required sections are complete
82- [ ] Output matches the user's stated need
83- [ ] Named frameworks are cited for key recommendations
84- [ ] No vague claims — every recommendation has a specific action
85- [ ] Deliverable is ready for operational use, not just conceptual
86 
87## Common Pitfalls
88 
891. **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
902. **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
913. **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
92 
93## Execution Artifacts
94 
95- `references/framework-notes.md` — HubSpot workflow enrollment, rep-triggered rules
96- `templates/output-template.md` — properties + workflow + sequence deliverable
97- `scripts/check-output.py` — local checklist validator
98This skill includes lightweight artifacts the agent can load on demand:
99- `references/enrichment-enrollment-gate.md` — lm_email_status workflow gate
100- `references/pat-spielmann-outbound-copy.md` — verify-before-enroll (Pat Spielmann)
101- `references/gtm-table-blueprints.md` — clay-toolkit property map
102- `references/leadmagic-waterfall.md` — loop list → workflow pattern
103- `references/gtm-experts-outbound-index.md` — expert router
104Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
105 
106## Implementation Depth
107 
108Use this section when the user asks for a finished asset, not a high-level explanation.
109 
110### Diagnostic Questions
111 
1121. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
1132. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
1143. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
1154. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
1165. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
117 
118### Framework Application
119 
120Map the recommendation explicitly to the named frameworks in this skill:
121 
122- HubSpot Sequences Best Practices: apply only the part that directly improves the requested deliverable.
123- ColdIQ Multi-Channel Cadence: apply only the part that directly improves the requested deliverable.
124- Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
125 
126### Deliverable Standard
127 
128A strong output from this skill includes:
129 
130- A crisp diagnosis of the current situation
131- A recommended path with tradeoffs, not a generic list
132- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
133- A measurement plan with leading and lagging indicators
134- Risks and edge cases called out before execution
135 
136### Adaptation Rules
137 
138- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
139- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
140- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
141 
142 
143## Related Skills
144- cold-email-strategy, cold-email-copywriting, sending-platforms, inbox-setup, email-deliverability
145 

Discussion

Alternatives

Browser Automation SkillWeb browser automation with AI-optimized snapshots for claude-flow agentsCoding · MITDeepevalDeepEval evaluation workflow for AI agents and LLM applications. TRIGGER when the user wants to evaluate or improve an AI agent, tool-using workflow, multi-turn chatbot, RAG pipeline, or LLM app; add evals; generate datasets or goldens; use deepeval generate; use deepeval test run; send results to Confident AI; monitor production; run online evals; inspect traces; or iterate on prompts, tools, retrieval, or agent behavior from eval failures. AI agents are the primary use case. Covers Python SDK, pytest eval suites, CLI generation, traced evals, Confident AI reporting, and agent-driven improvement loops. DO NOT TRIGGER for unrelated generic pytest, non-AI test setup, or non-DeepEval observability work unless the user asks to compare or migrate to DeepEval; for instrumenting an app with DeepEval tracing, @observe, or framework integrations (use the `deepeval-tracing` skill); or for raw OpenTelemetry / OTLP export without the deepeval package (use the `deepeval-otel` skill).Business & ops · Apache-2.0Dev browserBrowser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.Business & ops · MITTurn into appTurn visible project context, a proven thread, skill, or workflow into a runnable Agent-Native app with simple buttons, visible agent steps, preview, and deployment handoff. Use when a user invokes `/turn-into-app` or asks to make a workflow into an app, including from Claude or ChatGPT on the web, including when the source is a spreadsheet link or upload.Business & ops · MIT