HubSpot Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
HubSpot
Connector status: In progress
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Tajo’s HubSpot connector is in progress. The code exists, but it has not yet passed a run against a live HubSpot account.
What the code does
- Reads contacts, companies, deals, leads and tickets, 19 other CRM object types such as orders, carts, invoices and subscriptions, and custom objects.
- Reads owners, properties, lists and list memberships, forms and order pipelines.
- Reads email subscription preferences and opt-out status, to decide suppressions.
- Creates or updates a contact by email. This is its only write.
Not available today
- Two-way contact sync between HubSpot and Brevo
- Real-time updates. There are no HubSpot webhooks; records arrive when a sync reads them.
- Engagement history: email opens, calls, meetings and notes
- Workflow triggers from lifecycle stage changes
Open-Source Implementation Map
This section is derived from official or public repository material discovered for the HubSpot connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.
Repository Snapshot
| Repository | Commit | Languages / formats | Files |
|---|---|---|---|
| HubSpot/HubSpot-Public-API-Spec-Collection | 852bc16 | JSON (511), postman/api (1), postman/api_00f8c226-8513-4ea0-8592-ed2d246f258d (1), postman/api_02993b5c-6639-4475-8a76-b8ed19a52d3a (1), postman/api_03bbec65-b602-4556-b3ec-f032da516ef2 (1), postman/api_058ba0d6-3d29-4a4d-b8e8-1870a36cb2b1 (1) | 625 |
Integration Shape
graph LR Source["HubSpot API / repository"] --> Auth["Auth and scopes"] Source --> Objects["Objects, events, and schemas"] Auth --> Tajo["Tajo connector runtime"] Objects --> Tajo Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"] Tajo --> Ops["Backfill, cursor, retries, logs"]What To Reuse
- Postman Integration: Synchronization with HubSpot’s Public APIs via Open API 3.0 Schema
- Purpose
- Usage
- These specifications are not intended for external use. If you are an external developer looking for HubSpot’s API documentation, please refer to our official API documentation.
- Updating the Specifications
Tajo Revamp Checklist
- Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
- Map primary resources into explicit Tajo sync objects with stable external IDs.
- Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
- Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
- Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
- Keep examples small and runnable against sandbox or test-mode accounts.