HubSpot Notes Intelligence

Task

Pull notes for active deals and contacts using @HubSpot/List Notes and @HubSpot/Get NoteName it "HubSpot/Get Note" and call it with @HubSpot/Get Note, cross-referenced with @HubSpot/Search Deals and @HubSpot/Search ContactsName it "HubSpot/Search Contacts" and call it with @HubSpot/Search Contacts. Analyze free-text notes to extract key decisions, commitments, blockers, competitor mentions, and timeline references. Produce a structured summary and optionally update notes with tags via @HubSpot/Update NoteName it "HubSpot/Update Note" and call it with @HubSpot/Update Note.

Example: Scan all notes on deals closing this quarter and surface any commitments, blockers, or competitor mentions.

Input

The user will provide:

1. A scope for which notes to analyze (e.g., deals in a pipeline, contacts in a segment, or a specific deal/contact)
2. Optionally, what to extract (decisions, blockers, commitments, competitors, timelines)
3. Optionally, a time range for notes (default: last 30 days)

Example: "Analyze notes on all deals in the Enterprise pipeline from the last 30 days. Pull out any blockers or competitor mentions."

Context

What to Extract from Notes

Decisions:

• Agreements on pricing, terms, or scope
• Go/no-go decisions from the buyer
• Internal decisions about deal strategy

Commitments:

• Promised follow-ups ("I will send the proposal by Friday")
• Scheduled next steps ("Demo on March 15")
• Deliverables owed by either side

Blockers:

• Legal or procurement hold-ups
• Technical requirements not yet met
• Budget freezes or reorgs
• Missing stakeholder approval

Competitive intelligence:

• Mentions of specific competitors
• Feature comparisons or objections
• Pricing pressure from alternatives

Timeline references:

• Target close dates mentioned in notes
• Implementation timelines discussed
• Renewal or contract end dates

Analysis Strategy

1. Search for active deals or contacts matching the user's scope
2. List all notes associated with those records
3. Read each note's full content
4. Extract structured data: decisions, commitments, blockers, competitors, timelines
5. Cross-reference commitments against dates to flag overdue items
6. Group findings by deal or contact for easy review
7. Produce a summary report with actionable items

Data Quality Rules

• Distinguish between the user's own notes and notes from other team members
• Flag commitments with past-due dates as "overdue"
• If a note is ambiguous, include the original text alongside the extraction
• Never infer intent that is not explicitly stated in the note

Output

Notes Intelligence Summary:

Notes Analyzed: [count] Deals/Contacts Covered: [count] Decisions Found: [count] Open Commitments: [count] Blockers Identified: [count] Competitor Mentions: [count]

---

Open Commitments (Action Required):

| Deal/Contact | Commitment | Owner | Date Mentioned | Status | |-------------|------------|-------|----------------|--------| | [Deal] | Send revised proposal | [Rep] | Mar 5 | Overdue | | [Deal] | Schedule technical review | [Rep] | Mar 10 | Upcoming | | [Deal] | Provide security docs | [Buyer] | Mar 8 | Pending |

---

Blockers (Deals at Risk):

| Deal | Blocker | Source Note Date | Impact | |------|---------|-----------------|--------| | [Deal] | Legal review pending on MSA | [date] | Blocking close | | [Deal] | Budget freeze until Q2 | [date] | Timeline slip |

---

Competitor Mentions:

| Deal | Competitor | Context | Note Date | |------|-----------|---------|-----------| | [Deal] | [Competitor] | Buyer comparing pricing | [date] | | [Deal] | [Competitor] | Feature gap mentioned | [date] |

---

Key Decisions Logged:

1. [Deal] — Buyer agreed to annual billing ([date])
2. [Deal] — Scope reduced to Phase 1 only ([date])
3. [Deal] — Executive sponsor confirmed ([date])

---

Timeline References:

• [Deal]: Target close date mentioned as [date]
• [Deal]: Implementation kickoff planned for [date]