HubSpot User Guide
Prepare trustworthy HubSpot-backed context or a safely reviewed HubSpot action while keeping the surrounding Sales workflow authoritative for the business task.
Common Skill Instructions
MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.
HubSpot Operation Ranking
Use this priority order when the requested HubSpot job or record is ambiguous.
- Explicit user request, named record, HubSpot ID, company, deal, contact, ticket, or stated action
- Read-only CRM context needed by the active Sales workflow
- Exact record or a high-confidence candidate resolved from the user's words and business context
- The smallest property set, associations, activity context, or page of results that answers the request
- A reviewed draft of proposed HubSpot changes
- An explicitly approved, supported HubSpot write followed by verification
Do not silently pick among plausible records, broaden a read into a write, or treat clarification as write approval.
Key Dependency Categories
These are particularly important for this workflow; use your best judgment to potentially include other data sources to improve quality.
- ~~CRM, specifically the exposed HubSpot connector, for HubSpot-backed identity, records, properties, associations, links, and approved writes
- The parent Sales workflow for Calendar, Meeting Transcripts, Email, Internal Messaging, Knowledge & Files, or Sales Intelligence context that HubSpot does not own
- User-provided record IDs, names, exports, property values, and business context when connector access is unavailable or a record needs disambiguation
If HubSpot is missing, unavailable, stale, ambiguous, or limited by the exposed connector surface, say so and label the answer as not HubSpot-backed.
Workflow Guidance
These HubSpot-specific steps override the default workflow in the index skill.
- Resolve access and target
- Use get_user_details first to confirm the connected portal and exposed object read/write availability.
- Resolve whether the user wants a read, a draft, or an approved write; identify object type, owner or team, pipeline, timeframe, stage, and exact record when those affect the answer.
- For an ambiguous record, do the smallest bounded candidate lookup and ask the user to choose before using it for a summary or write.
- Discover properties and records
- Use search_properties with at most five focused keywords when fields are uncertain; use get_properties to confirm enum values and writable properties.
- Use search_crm_objects for search, counts, filters, pagination, and associations. Use get_crm_objects for known IDs. Do not use deprecated search or fetch.
- Retrieve only the properties and associations that affect the sales decision. State filters, totals, page or sample limits, and whether analysis is sampled.
- Draft, approve, and verify
- For proposed changes, show an exact field-level draft before calling manage_crm_objects.
- Write only after the user explicitly approves the exact reviewed change or batch. Batch at most 10 objects and confirm associations separately.
- A reviewed-batch approval applies only to that exact batch; never offer a blanket confirmation bypass.
- Inspect the write response and verify with a narrow read when the response does not prove the outcome.
HubSpot Rules
- Prefer exact IDs, domains, emails, and full names plus company over vague name-only matching.
- Before querying or writing with a property or enum, confirm property labels, internal names, enum values, and writeability; do not guess them.
- Keep HubSpot as CRM truth for HubSpot-owned account, contact, deal, ticket, owner, pipeline, and activity facts. Do not let enrichment or web context overwrite CRM truth.
- Include clickable connector-returned or trusted HubSpot record URLs with UTM parameters when available.
- Do not write inferred data, overwrite user-entered context without clear consent, or mutate an association without explicit approval.
- Do not imply support for objects, properties, pagination behavior, bulk sizes, or writes that the live connector does not expose.
Connector Boundary
Use only the HubSpot surfaces that are actually exposed:
- Identity and access: get_user_details
- Property discovery: search_properties, get_properties
- Record search and reads: search_crm_objects, get_crm_objects
- Reviewed writes: manage_crm_objects
For unsupported broad exports, delete, merge, dedupe, arbitrary automation, or unexposed object operations, state the missing surface and offer a narrower read, a draft, or another approved source.
Modes
1. HubSpot Read
- Use for company, deal, contact, ticket, owner, activity, property, or association context.
- Resolve the target, retrieve only decision-relevant fields, and call out ambiguity or gaps.
Output Format
# [HubSpot Record Or Context]
## Summary
- [Most important CRM fact with trusted link]
- [Current deal, company, contact, activity, or association signal]
- [Risk, missing property, ambiguity, or source gap]
---
{Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}
{Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}
2. HubSpot Update Draft
- Use when the user asks to prepare a note, property change, association, create, or update but has not approved the write.
- Keep current and proposed values separate and identify the exact target.
Output Format
# Proposed HubSpot Update
**Target:** [Record name, type, and trusted link or ID]
| Property / Association | Current Value | Proposed Value | Reason / Source |
| --- | --- | --- | --- |
| [Label] | [Current or Unknown] | [Proposed] | [Grounded reason + link] |
## Before I Write
- [Missing input, association confirmation, validation risk, or approval needed]
---
{Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}
{Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}
3. Approved HubSpot Write
- Use only after explicit approval for the exact reviewed object or batch.
- Verify before reporting completion when the write response is inconclusive.
Output Format
# HubSpot Updated
**Record:** [Name, type, and trusted link or ID]
- **Changed:** [Property or association]
- **Result:** [Verified outcome]
- **Not changed:** [Unsupported or skipped item]
---
{Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}
{Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}
1---2name: hubspot3description: Use only when a focused Sales workflow has selected a connected HubSpot CRM, or the user explicitly asks for HubSpot guidance, reads, drafts, notes, or reviewed record changes. Do not use when another CRM is authoritative.4metadata:5 source: https://skillmd.com/skills/openai/hubspot6---78# HubSpot User Guide910Prepare trustworthy HubSpot-backed context or a safely reviewed HubSpot action while keeping the surrounding Sales workflow authoritative for the business task.1112## Common Skill Instructions1314MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.1516## HubSpot Operation Ranking1718Use this priority order when the requested HubSpot job or record is ambiguous.19201. Explicit user request, named record, HubSpot ID, company, deal, contact, ticket, or stated action212. Read-only CRM context needed by the active Sales workflow223. Exact record or a high-confidence candidate resolved from the user's words and business context234. The smallest property set, associations, activity context, or page of results that answers the request245. A reviewed draft of proposed HubSpot changes256. An explicitly approved, supported HubSpot write followed by verification2627Do not silently pick among plausible records, broaden a read into a write, or treat clarification as write approval.2829## Key Dependency Categories3031These are particularly important for this workflow; use your best judgment to potentially include other data sources to improve quality.3233- ~~CRM, specifically the exposed HubSpot connector, for HubSpot-backed identity, records, properties, associations, links, and approved writes34- The parent Sales workflow for Calendar, Meeting Transcripts, Email, Internal Messaging, Knowledge & Files, or Sales Intelligence context that HubSpot does not own35- User-provided record IDs, names, exports, property values, and business context when connector access is unavailable or a record needs disambiguation3637If HubSpot is missing, unavailable, stale, ambiguous, or limited by the exposed connector surface, say so and label the answer as not HubSpot-backed.3839## Workflow Guidance4041These HubSpot-specific steps override the default workflow in the index skill.4243- 1. Resolve access and target44 - Use get_user_details first to confirm the connected portal and exposed object read/write availability.45 - Resolve whether the user wants a read, a draft, or an approved write; identify object type, owner or team, pipeline, timeframe, stage, and exact record when those affect the answer.46 - For an ambiguous record, do the smallest bounded candidate lookup and ask the user to choose before using it for a summary or write.47- 2. Discover properties and records48 - Use search_properties with at most five focused keywords when fields are uncertain; use get_properties to confirm enum values and writable properties.49 - Use search_crm_objects for search, counts, filters, pagination, and associations. Use get_crm_objects for known IDs. Do not use deprecated search or fetch.50 - Retrieve only the properties and associations that affect the sales decision. State filters, totals, page or sample limits, and whether analysis is sampled.51- 3. Draft, approve, and verify52 - For proposed changes, show an exact field-level draft before calling manage_crm_objects.53 - Write only after the user explicitly approves the exact reviewed change or batch. Batch at most 10 objects and confirm associations separately.54 - A reviewed-batch approval applies only to that exact batch; never offer a blanket confirmation bypass.55 - Inspect the write response and verify with a narrow read when the response does not prove the outcome.5657## HubSpot Rules5859- Prefer exact IDs, domains, emails, and full names plus company over vague name-only matching.60- Before querying or writing with a property or enum, confirm property labels, internal names, enum values, and writeability; do not guess them.61- Keep HubSpot as CRM truth for HubSpot-owned account, contact, deal, ticket, owner, pipeline, and activity facts. Do not let enrichment or web context overwrite CRM truth.62- Include clickable connector-returned or trusted HubSpot record URLs with UTM parameters when available.63- Do not write inferred data, overwrite user-entered context without clear consent, or mutate an association without explicit approval.64- Do not imply support for objects, properties, pagination behavior, bulk sizes, or writes that the live connector does not expose.6566## Connector Boundary6768Use only the HubSpot surfaces that are actually exposed:6970- Identity and access: get_user_details71- Property discovery: search_properties, get_properties72- Record search and reads: search_crm_objects, get_crm_objects73- Reviewed writes: manage_crm_objects7475For unsupported broad exports, delete, merge, dedupe, arbitrary automation, or unexposed object operations, state the missing surface and offer a narrower read, a draft, or another approved source.7677## Modes7879### 1. HubSpot Read8081- Use for company, deal, contact, ticket, owner, activity, property, or association context.82- Resolve the target, retrieve only decision-relevant fields, and call out ambiguity or gaps.8384#### Output Format8586 # [HubSpot Record Or Context]8788 ## Summary8990 - [Most important CRM fact with trusted link]91 - [Current deal, company, contact, activity, or association signal]92 - [Risk, missing property, ambiguity, or source gap]9394 ---9596 {Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}9798 {Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}99100### 2. HubSpot Update Draft101102- Use when the user asks to prepare a note, property change, association, create, or update but has not approved the write.103- Keep current and proposed values separate and identify the exact target.104105#### Output Format106107 # Proposed HubSpot Update108109 **Target:** [Record name, type, and trusted link or ID]110111 | Property / Association | Current Value | Proposed Value | Reason / Source |112 | --- | --- | --- | --- |113 | [Label] | [Current or Unknown] | [Proposed] | [Grounded reason + link] |114115 ## Before I Write116117 - [Missing input, association confirmation, validation risk, or approval needed]118119 ---120121 {Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}122123 {Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}124125### 3. Approved HubSpot Write126127- Use only after explicit approval for the exact reviewed object or batch.128- Verify before reporting completion when the write response is inconclusive.129130#### Output Format131132 # HubSpot Updated133134 **Record:** [Name, type, and trusted link or ID]135136 - **Changed:** [Property or association]137 - **Result:** [Verified outcome]138 - **Not changed:** [Unsupported or skipped item]139140 ---141142 {Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}143144 {Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}