HueLifeCMO Knowledge Base

HubSpot Claude Connector — Playbook for Tickets / Pipelines / Segments

Concrete example prompts for the things the read-only hs CLI (Path A) can't reach. These run in the Claude app (claude.ai / desktop / mobile) with the HubSpot connector connected — not in Claude Code. See CLAUDE.md → "HubSpot access — TWO paths."

Before you start (once)

  1. In the Claude app → Settings → Connectors → connect HubSpot (OAuth, pick the HueLife account 44205564).
  2. Set HubSpot connector → Write tools → "Needs Approval" so Claude shows every change before it executes. (All writes also land in HubSpot's Audit Log.)
  3. Remember the limits: bulk writes capped at 10 records/turn, and custom validation rules aren't enforced by the connector — eyeball data integrity.

Tip: start each working session with "Confirm you're connected to HubSpot account 44205564 (HueLife) and list what objects you can access."

1. Pipelines & deal stages

(Path A was blocked here — "user-level token not allowed." Use the connector.) Context: HueLife currently has only 3 deals, so this is mostly about standing up pipeline usage, not cleaning it.

Read / inspect - "List my deal pipelines and all their stages, in order." - "Show me every deal and which stage it's in." - "Are there any pipeline stages that no deal has ever been in?"

Set up / fix (with approval) - "Create a deal pipeline called Course Sales with stages: Inquiry → Proposal → Enrolled → Delivered → Closed Lost." (verify it can create pipelines; if not, it'll say so and you create the pipeline in-app, then use Claude for the deals.) - "Create a deal named 'Acme Org — Q3 Facilitation', $5,000, in the Inquiry stage, associated with company Acme Org." → approve. - "Move deal 'Acme Org — Q3 Facilitation' to Proposal and log a note: sent proposal 6/2."

Report - "Summarize open deals by stage with total value, and flag any with no activity in 30 days."

2. Tickets

(Not scoped on the PAK. Connector covers tickets natively.)

Read / triage - "List open tickets, grouped by status and owner." - "Which tickets have been open longest with no reply?" - "Summarize this week's tickets and the top 3 recurring themes."

Create / update (with approval) - "Create a ticket: subject 'Course login broken — Jane Doe', priority High, associate it with Jane Doe's contact." → approve. - "Move ticket #123 to Waiting on customer and log a note."

If HueLife isn't using Service Hub/tickets yet, ask: "Do we have a ticket pipeline set up? If not, what stages would you recommend for a small training org?"

3. Segments & lists

(Not scoped on the PAK. This is where the connector shines for a CMO.) This ties directly to the audit's dead-field finding — use segments to activate fields by targeting who needs them filled.

Explore / build - "How many contacts have a value for course_participation? Build a list of those — call it Active Course Participants." - "Find contacts created this year with a corporate (non-Gmail/Yahoo/Outlook.com) email — these are the B2B-enrichable segment from the audit." - "Show contacts with no Lifecycle Stage set, so we can fix the gap." - "Create a segment of contacts who attended a course but have no photo_release value — that's our consent-collection follow-up list."

Act on a segment (mind the 10-record cap) - "For the first 10 contacts in Active Course Participants with empty Lifecycle Stage, propose setting it to Customer." → review → approve. (Repeat in batches, or do bulk updates in-app for large sets.)

4. Audit-gap closers (quick wins)

When to switch back to Path A (the CLI, here)

Reality check: the connector proposes; you approve. Treat the first few writes as a trust-building exercise — verify each landed correctly in HubSpot before doing bulk.