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. Use when: hubspot, hubspot api, hubspot crm, hubspot integration, contacts api.
HubSpot Integration - CRM API Integration Expert Mode
Skills Overview
HubSpot Integration provides a comprehensive HubSpot CRM API integration guide, covering OAuth authentication, CRM object operations, bulk processing, webhooks, and custom objects. It supports both Node.js and Python SDKs.
Use Cases
-
SaaS Products and HubSpot Integration When your product needs to sync customer HubSpot CRM data bidirectionally, this skill offers end-to-end solutions for OAuth authentication, data mapping, and error handling.
-
Enterprise Internal Data Automation When you need to automatically sync data from internal systems (e.g., ERP, order systems) to HubSpot, or retrieve customer data from HubSpot for business analytics.
-
Custom Development for HubSpot When you need to create custom objects, extend CRM capabilities, or implement business logic and data processing workflows that HubSpot doesn’t natively support.
Core Features
-
Secure Authentication System
- OAuth 2.0: Secure authorization flow for public applications
- Private App Token: Simplified authentication for single-account integration scenarios
- Helps you choose the correct authentication method and avoid deprecated API keys
-
Full Lifecycle Management of CRM Objects
- CRUD operations for standard objects such as contacts, companies, deals, and tickets
- Creating and querying associations
- Creating and managing custom objects
- Optimizing API call efficiency with bulk operations
-
Real-Time Data Processing
- Webhook configuration and event subscriptions
- Incremental sync as an alternative to polling
- Error retries and idempotency design
Common Questions
What authentication methods does the HubSpot API offer? How should I choose?
The HubSpot API provides three main authentication methods:
- OAuth 2.0: Recommended for public applications for multiple customers; it’s the safest option
- Private App Token: Suitable for internal integrations for a single account; easy to configure but limited to your own account
- API Key (deprecated): No longer recommended by the official guidance; existing projects should migrate to OAuth
Recommendation:
- If you’re developing an application for the public, you must use OAuth 2.0.
- If it’s an internal tool integration, Private App is simpler and faster.
What advantages do batch operations have over single requests?
Batch operations (Batch Operations) can significantly improve performance:
- Higher efficiency: One API call can process up to 100 records
- Quota optimization: Batch operations consume 1 quota unit instead of 100
- Lower cost: Reduces network round trips and the number of API calls
Example scenario: Sync 1,000 contacts. With batch operations, it takes only 10 requests; with single requests, it requires 1,000 requests and may trigger rate limits.
What’s the difference between webhooks and polling? Which should I use?
| Feature | Webhooks | Polling |
|---|---|---|
| Timeliness | Real-time push | Delays depend on the polling interval |
| Resource consumption | Low (event-driven) | High (continuous requests) |
| Implementation complexity | Requires a receiver endpoint | Simple and straightforward |
Use Webhooks unless:
- Your receiving service cannot expose a public endpoint
- You need to backfill historical data
- Your webhook configuration environment is limited
This skill covers the complete webhook configuration process, including event subscriptions, signature verification, and retry handling.