HubSpot Integration workflow skill. Use this skill when the user needs Expert patterns for HubSpot CRM integration including OAuth and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
HubSpot Integration workflow skill. Use this skill when the user needs Expert patterns for HubSpot CRM integration including OAuth and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills/skills/hubspot-integration from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
HubSpot Integration Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Patterns, Sharp Edges, Validation Checks, Collaboration, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
User mentions or implies: hubspot
User mentions or implies: hubspot api
User mentions or implies: hubspot crm
User mentions or implies: hubspot integration
User mentions or implies: contacts api
Use when the request clearly matches the imported source intent: Expert patterns for HubSpot CRM integration including OAuth.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Patterns
OAuth 2.0 Authentication
Secure authentication for public apps
When to use: Building public app or multi-account integration
Template
// OAuth 2.0 flow for HubSpot
import { Client } from "@hubspot/api-client";
// BATCH READ contacts by ID
async function batchReadContacts(
ids: string[],
properties: string[] = ["firstname", "lastname", "email"]
) {
const response = await hubspotClient.crm.contacts.batchApi.read({
inputs: ids.map((id) => ({ id })),
properties,
});
return response.results;
}
// BATCH ARCHIVE contacts
async function batchDeleteContacts(ids: string[]) {
await hubspotClient.crm.contacts.batchApi.archive({
inputs: ids.map((id) => ({ id })),
});
}
// Process large dataset in chunks
async function processLargeDataset(allContacts: any[]) {
const BATCH_SIZE = 100;
const results = [];
for (let i = 0; i < allContacts.length; i += BATCH_SIZE) {
const batch = allContacts.slice(i, i + BATCH_SIZE);
const batchResults = await batchCreateContacts(batch);
results.push(...batchResults);
// Respect rate limits - wait between batches
if (i + BATCH_SIZE < allContacts.length) {
await sleep(100); // 100ms between batches
}
}
return results;
}
Notes
Max 100 items per batch request
Saves up to 80% of rate limit quota
Batch operations are atomic per item (partial success possible)
Check response.errors for failed items
Associations v4 API
Create relationships between CRM records
When to use: Linking contacts to companies, deals, etc.
Template
import { Client, AssociationTypes } from "@hubspot/api-client";
const hubspotClient = new Client({
accessToken: process.env.HUBSPOT_TOKEN,
});
// GET associations for a record
async function getContactCompanies(contactId: string) {
const response = await hubspotClient.crm.associations.v4.basicApi.getPage(
"contacts",
contactId,
"companies",
undefined,
500
);
return response.results;
}
// CREATE association with custom label
async function createLabeledAssociation(
contactId: string,
companyId: string,
labelId: number // Custom association label ID
) {
await hubspotClient.crm.associations.v4.basicApi.create(
"contacts",
contactId,
"companies",
companyId,
[
{
associationCategory: "USER_DEFINED",
associationTypeId: labelId,
},
]
);
}
// Common association type IDs
// Contact to Company: 1
// Company to Contact: 2
// Deal to Contact: 3
// Contact to Deal: 4
// Deal to Company: 5
// Company to Deal: 6
Notes
Requires SDK version 9.0.0+ for v4 API
Association labels supported for custom relationships
Use batch API for multiple associations
HUBSPOT_DEFINED for standard, USER_DEFINED for custom labels
Webhook Handling
Receive real-time notifications from HubSpot
When to use: Need instant updates on CRM changes
Template
import crypto from "crypto";
import { Client } from "@hubspot/api-client";
Can associate with standard and other custom objects
Examples
Example 1: Ask for the upstream workflow directly
Use @hubspot-integration-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @hubspot-integration-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @hubspot-integration-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @hubspot-integration-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/hubspot-integration, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Sharp Edges
Rate Limits Vary by App Type and Hub Tier
Severity: HIGH
5% Error Rate Threshold for Marketplace Apps
Severity: HIGH
API Keys Deprecated - Use OAuth or Private App Tokens
Severity: CRITICAL
OAuth Access Tokens Expire in 30 Minutes
Severity: HIGH
Webhook Requests Must Be Validated
Severity: CRITICAL
All List Endpoints Require Pagination
Severity: MEDIUM
Associations v4 API Has Breaking Changes
Severity: HIGH
Polling Limited to 100,000 Requests Per Day
Severity: MEDIUM
Imported: Validation Checks
Hardcoded HubSpot API Key
Severity: ERROR
API keys must never be hardcoded
Message: Hardcoded HubSpot API key detected. Use environment variables. Note: API keys are deprecated - use Private App tokens.
Hardcoded HubSpot Access Token
Severity: ERROR
Access tokens must use environment variables
Message: Hardcoded HubSpot access token. Use environment variables.
Hardcoded Client Secret
Severity: ERROR
OAuth client secrets must be secured
Message: Hardcoded client secret. Use environment variables.
Missing Webhook Signature Validation
Severity: ERROR
Webhook endpoints must validate HubSpot signatures
Message: Webhook endpoint without signature validation. Validate X-HubSpot-Signature-v3.
Missing Rate Limit Handling
Severity: WARNING
API calls should handle 429 responses
Message: HubSpot API calls without rate limit handling. Implement retry logic with backoff.
Unthrottled Parallel API Calls
Severity: WARNING
Parallel calls can exceed rate limits
Message: Parallel HubSpot API calls without throttling. Use rate limiter.
Missing Pagination for List Calls
Severity: WARNING
List endpoints return paginated results
Message: API call without pagination handling. Implement cursor-based pagination.
Individual Operations in Loop
Severity: INFO
Use batch operations for multiple items
Message: Individual API calls in loop. Consider batch operations for better performance.
Token Storage Without Expiry
Severity: WARNING
OAuth tokens expire and need refresh logic
Message: Token storage without expiry tracking. Store expiresAt for refresh logic.
Deprecated API Key Usage
Severity: ERROR
API keys are deprecated
Message: Using deprecated API key. Migrate to Private App token or OAuth 2.0.
