@rawdash/connector-hubspot 0.15.0 → 0.17.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/README.md CHANGED
@@ -1,114 +1,84 @@
1
+ <!-- This file is generated from connector metadata by scripts/generate-connector-docs.ts. Do not edit by hand. -->
2
+
1
3
  # @rawdash/connector-hubspot
2
4
 
3
- Rawdash connector for HubSpot — syncs CRM contacts, companies, and deals, deal stage-change events, and marketing email campaign performance into the six-shape storage model. Covers both the sales (pipeline, win rate) and marketing (email engagement) verticals from a single connector.
5
+ [![npm version](https://img.shields.io/npm/v/@rawdash/connector-hubspot)](https://www.npmjs.com/package/@rawdash/connector-hubspot)
6
+ [![license](https://img.shields.io/npm/l/@rawdash/connector-hubspot)](https://github.com/rawdash/rawdash/blob/main/LICENSE)
7
+
8
+ Sync CRM contacts, companies, and deals plus deal stage-change events and marketing email campaign stats from HubSpot.
9
+
10
+ ## Install
4
11
 
5
- ## Auth setup
12
+ ```sh
13
+ npm install @rawdash/connector-hubspot
14
+ ```
6
15
 
7
- The connector authenticates with a **private app access token**.
16
+ ## Authentication
8
17
 
9
- 1. In HubSpot, go to **Settings Integrations Private Apps**.
10
- 2. Click **Create a private app**.
11
- 3. On the **Basic Info** tab, give it a name (e.g. `rawdash`).
12
- 4. On the **Scopes** tab, enable read access for the resources you want to sync:
13
- - `crm.objects.contacts.read`
14
- - `crm.objects.companies.read`
15
- - `crm.objects.deals.read`
16
- - `marketing-email` (only needed for `email_campaigns` / `email_stats`)
17
- 5. Click **Create app**, then **Continue creating** to confirm.
18
- 6. Open the app's **Auth** tab and copy the **Access token** (starts with `pat-`).
18
+ A HubSpot private app access token with read scopes for the resources you sync (contacts, companies, deals, and marketing email).
19
19
 
20
- > **Note:** The token only needs read scopes for the resources you actually sync. Pick the narrowest set that covers your dashboards.
20
+ 1. In HubSpot, go to Settings Integrations Private Apps and create a private app.
21
+ 2. Grant read scopes for the resources you intend to sync (CRM contacts, companies, deals, and marketing email).
22
+ 3. Copy the generated access token (starts with `pat-`).
23
+ 4. Store it as a secret and reference it from the connector config as `accessToken: secret("HUBSPOT_ACCESS_TOKEN")`.
21
24
 
22
25
  ## Configuration
23
26
 
27
+ | Field | Type | Required | Description |
28
+ | ------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
29
+ | `accessToken` | secret | Yes | HubSpot private app access token with read scopes for contacts, companies, deals, and marketing email. Create one at Settings → Integrations → Private Apps. |
30
+ | `resources` | array | No | Which HubSpot resources to sync. Omit to sync all resources. The access token only needs read scopes for the resources listed here. |
31
+
32
+ ## Resources
33
+
34
+ - **`hubspot_contact`** _(entity)_ - CRM contacts with email, lifecycle stage, lead status, owner, and creation time.
35
+ - Endpoint: `POST /crm/v3/objects/contacts/search`
36
+ - **`hubspot_company`** _(entity)_ - CRM companies with name, domain, industry, lifecycle stage, and creation time.
37
+ - Endpoint: `POST /crm/v3/objects/companies/search`
38
+ - **`hubspot_deal`** _(entity)_ - CRM deals with name, stage, pipeline, amount, close date, owner, and creation time.
39
+ - Endpoint: `POST /crm/v3/objects/deals/search`
40
+ - **`hubspot_deal_stage_change`** _(event)_ - Deal stage-change events derived from deal property history, one event per stage transition.
41
+ - Endpoint: `GET /crm/v3/objects/deals?propertiesWithHistory=dealstage`
42
+ - **`hubspot_email_campaign`** _(entity)_ - Marketing email campaigns with name, subject, sender, type, send date, and recipient count.
43
+ - Endpoint: `GET /email/public/v1/campaigns`
44
+ - **`hubspot_email_stats`** _(metric)_ - Per-campaign marketing email engagement stats (sent, delivered, opened, clicked, bounced, unsubscribed) timestamped at the campaign send time.
45
+ - Endpoint: `GET /email/public/v1/campaigns/{id}`
46
+ - Unit: emails
47
+ - Dimensions: `campaignId`, `campaignName`, `delivered`, `opened`, `clicked`, `bounced`, `unsubscribed`
48
+ - One sample per campaign; value is the sent count, and every counter (delivered, opened, clicked, bounced, unsubscribed) is also exposed in attributes.
49
+
50
+ ## Example
51
+
24
52
  ```ts
25
- import { secret } from '@rawdash/core';
53
+ import {
54
+ defineConfig,
55
+ defineDashboard,
56
+ defineMetric,
57
+ secret,
58
+ } from '@rawdash/core';
26
59
 
27
60
  const hubspot = {
28
61
  name: 'hubspot',
29
62
  connectorId: 'hubspot',
30
63
  config: {
31
64
  accessToken: secret('HUBSPOT_ACCESS_TOKEN'),
32
- // resources: ['contacts', 'deals', 'deal_events'], // optional, defaults to all
65
+ resources: ['contacts', 'companies', 'deals'],
33
66
  },
34
67
  };
35
- ```
36
-
37
- Register the connector class when mounting the engine:
38
-
39
- ```ts
40
- import { HubSpotConnector } from '@rawdash/connector-hubspot';
41
- import { mountEngine } from '@rawdash/hono';
42
-
43
- mountEngine(config, { connectorRegistry: { hubspot: HubSpotConnector } });
44
- ```
45
-
46
- ### Choosing resources
47
-
48
- By default the connector syncs every supported resource. To sync only a subset, pass `resources` with any combination of:
49
-
50
- `contacts`, `companies`, `deals`, `deal_events`, `email_campaigns`, `email_stats`
51
-
52
- The access token only needs read scopes for the resources you list, and picking only what you need reduces API calls during full syncs.
53
-
54
- ### Example dashboard
55
-
56
- ```ts
57
- import { defineConfig, defineDashboard, defineMetric } from '@rawdash/core';
58
68
 
59
69
  export default defineConfig({
60
70
  connectors: [hubspot],
61
71
  dashboards: {
62
72
  sales: defineDashboard({
63
73
  widgets: {
64
- open_deal_value: {
65
- kind: 'stat',
66
- title: 'Open deal value',
67
- metric: defineMetric({
68
- connector: hubspot,
69
- shape: 'entity',
70
- entityType: 'hubspot_deal',
71
- field: 'amount',
72
- fn: 'sum',
73
- filter: [{ field: 'dealStage', op: 'neq', value: 'closedlost' }],
74
- }),
75
- },
76
74
  open_deals: {
77
75
  kind: 'stat',
78
- title: 'Open deals',
76
+ title: 'Open Deals',
79
77
  metric: defineMetric({
80
78
  connector: hubspot,
81
79
  shape: 'entity',
82
80
  entityType: 'hubspot_deal',
83
81
  fn: 'count',
84
- filter: [
85
- { field: 'dealstage', op: 'eq', value: 'appointmentscheduled' },
86
- ],
87
- }),
88
- },
89
- contacts_by_lifecycle: {
90
- kind: 'distribution',
91
- title: 'Contacts by lifecycle stage',
92
- metric: defineMetric({
93
- connector: hubspot,
94
- shape: 'entity',
95
- entityType: 'hubspot_contact',
96
- fn: 'count',
97
- groupBy: { field: 'lifecycleStage' },
98
- }),
99
- },
100
- email_opens: {
101
- kind: 'timeseries',
102
- title: 'Email opens per campaign',
103
- window: '90d',
104
- metric: defineMetric({
105
- connector: hubspot,
106
- shape: 'metric',
107
- name: 'hubspot_email_stats',
108
- field: 'opened',
109
- fn: 'sum',
110
- window: '90d',
111
- groupBy: { field: 'ts', granularity: 'day' },
112
82
  }),
113
83
  },
114
84
  },
@@ -117,64 +87,22 @@ export default defineConfig({
117
87
  });
118
88
  ```
119
89
 
120
- ## Data model
121
-
122
- Monetary amounts (deal `amount`) are in the account's currency, as returned by HubSpot. Timestamps stored in attributes are Unix milliseconds.
90
+ ## Rate limits
123
91
 
124
- | Storage shape | Entity/event/metric type | Key attributes |
125
- | ------------- | --------------------------- | --------------------------------------------------------------------------------- |
126
- | entity | `hubspot_contact` | email, lifecycleStage, leadStatus, ownerId, createdAt |
127
- | entity | `hubspot_company` | name, domain, industry, lifecycleStage, createdAt |
128
- | entity | `hubspot_deal` | dealName, dealStage, pipeline, amount, closeDate, ownerId, createdAt |
129
- | event | `hubspot_deal_stage_change` | dealId, stage, sourceType |
130
- | entity | `hubspot_email_campaign` | name, subject, fromName, type, sentDate, numIncluded |
131
- | metric | `hubspot_email_stats` | campaignId, campaignName, sent, delivered, opened, clicked, bounced, unsubscribed |
92
+ HubSpot allows 100 requests / 10s; the Search API caps results at 10,000 per query.
132
93
 
133
- - **`hubspot_deal_stage_change`** events come from the `dealstage` property history on each deal (`propertiesWithHistory=dealstage`). One event per recorded stage value, timestamped at the moment the stage was set.
134
- - **`hubspot_email_stats`** metrics carry one sample per campaign; `value` is the `sent` count and every counter is also exposed in `attributes` so timeseries / distribution widgets can chart any of them.
94
+ ## Limitations
135
95
 
136
- ## Schemas
96
+ - Deal stage-change events are rewritten on every sync because the deal list endpoint has no incremental `since` filter.
97
+ - Marketing email campaign data comes from the legacy email campaigns API and is only available for marketing emails.
98
+ - Very large CRM portfolios may not backfill in full because the Search API caps at 10,000 results per query.
137
99
 
138
- `HubSpotConnector.schemas` declares the Zod schema for each resource's raw API response (the array of records for CRM resources, the deal-history record array, and the campaign-detail object array). Used by the cloud shape-drift pipeline to populate `connector_baselines`, and by the package's property tests.
100
+ ## Links
139
101
 
140
- ## Sync behaviour
141
-
142
- - **Backfill** (`mode: 'full'`): CRM objects are fetched via the Search API (`POST /crm/v3/objects/{object}/search`) sorted by last-modified ascending, paginated with the `after` cursor; deal events and email data are enumerated and rewritten in full.
143
- - **Incremental** (`mode: 'latest'`): CRM searches add a `filterGroups` `GTE` filter on the object's last-modified property so only changed records are fetched. Entity phases upsert (no clear); the event and metric phases rewrite their requested window each run.
144
- - **Resumable**: each phase yields an `after`/offset cursor on abort, so an interrupted sync resumes from the same page.
145
- - **Rate limits**: HubSpot returns `429` when the per-app limit (100 requests / 10s) is exceeded. The shared HTTP client retries automatically with exponential back-off and honors `Retry-After`.
146
-
147
- > **Search API ceiling:** HubSpot's Search API caps results at 10,000 per query. Very large CRM portfolios may not backfill in full in a single window; incremental syncs (which filter on `hs_lastmodifieddate`) stay well under the ceiling.
148
-
149
- ## Aggregates
150
-
151
- | Function | Resource | Upstream call |
152
- | -------- | ----------------- | ------------------------------------------------------------ |
153
- | `count` | `hubspot_contact` | `POST /crm/v3/objects/contacts/search` (`limit=1`, `total`) |
154
- | `count` | `hubspot_company` | `POST /crm/v3/objects/companies/search` (`limit=1`, `total`) |
155
- | `count` | `hubspot_deal` | `POST /crm/v3/objects/deals/search` (`limit=1`, `total`) |
156
-
157
- `count` widgets are served directly from the Search API `total`, so the runner can skip backfilling the underlying entities for that tick. Filter conditions translate to HubSpot search operators (`eq→EQ`, `neq→NEQ`, `gt→GT`, `gte→GTE`, `lt→LT`, `lte→LTE`, `contains→CONTAINS_TOKEN`). `OR` clauses and `latest` aggregates aren't supported and fall back to evaluating against synced storage rows.
158
-
159
- ## Registering in the MCP server
160
-
161
- To make the connector available via the `add_connector` MCP tool, include it in `connectorFactories`:
162
-
163
- ```ts
164
- import { HubSpotConnector, configFields } from '@rawdash/connector-hubspot';
165
-
166
- createMcpServer({
167
- // ...
168
- connectorFactories: [
169
- {
170
- id: 'hubspot',
171
- configFields,
172
- create: HubSpotConnector.create,
173
- },
174
- ],
175
- });
176
- ```
102
+ - [Rawdash docs](https://rawdash.dev/docs/connectors/)
103
+ - [HubSpot API docs](https://developers.hubspot.com/docs/api/overview)
104
+ - [GitHub](https://github.com/rawdash/rawdash)
177
105
 
178
- ## Property tests
106
+ ## License
179
107
 
180
- The CRM entity resources (`contacts`, `companies`, `deals`) have fast-check property tests under `src/property.test.ts` that generate synthetic API payloads from each resource's Zod schema, run them through `connector.sync()` against an `InMemoryStorage`, and assert universal invariants (non-empty ids, finite timestamps, no `undefined` in storage, no thrown errors) plus per-resource entity counts. Deal events, email campaigns, and email stats are covered by example-driven unit tests in `src/hubspot.test.ts`.
108
+ Apache-2.0