From f101c6c953e6bcd811762d55b92277915b6cf7e3 Mon Sep 17 00:00:00 2001 From: Cobalt0s Date: Sat, 30 May 2026 02:15:37 +0300 Subject: [PATCH 1/2] [ENG-3949] feat(hubspot): Event Occurrences --- src/provider-guides/hubspot.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/provider-guides/hubspot.mdx b/src/provider-guides/hubspot.mdx index 35301890..dc0da510 100644 --- a/src/provider-guides/hubspot.mdx +++ b/src/provider-guides/hubspot.mdx @@ -57,6 +57,17 @@ The connector supports reading from: The connector supports reading from: - [meeting-links](https://developers.hubspot.com/docs/api-reference/latest/scheduler/meetings/get-meeting-links) +#### Event Occurrences +The connector reads HubSpot event occurrences (the [Events API](https://developers.hubspot.com/docs/api-reference/latest/events/retrieve-events/get-events)). +Connector exposes occurrences as separate *custom objects* whose names are constructed by combining a fixed *prefix* with the *event type* name. +* Naming rule: `AMPERSAND-event-occurrences-`: + * AMPERSAND-event-occurrences-e_call_ended + * AMPERSAND-event-occurrences-e_form_submission + * AMPERSAND-event-occurrences-e_mta_bounced_email_v2 + * AMPERSAND-event-occurrences-e_visited_page + +Where to get the event type name: event type identifiers are returned by the Events API's [event types endpoint](https://developers.hubspot.com/docs/api-reference/latest/events/retrieve-events/get-event-types). + #### Reading users and owners To read users from your customer's HubSpot workspace, enable the `crm.objects.users.read` scope and add `users` as an object in `amp.yaml`: From e823ed656b94d7800fff86fcff0a109da47604b0 Mon Sep 17 00:00:00 2001 From: Cobalt0s Date: Fri, 5 Jun 2026 21:10:21 +0300 Subject: [PATCH 2/2] address comments --- src/provider-guides/hubspot.mdx | 33 ++++++++++++++++++++++++--------- 1 file changed, 24 insertions(+), 9 deletions(-) diff --git a/src/provider-guides/hubspot.mdx b/src/provider-guides/hubspot.mdx index dc0da510..23c6a9aa 100644 --- a/src/provider-guides/hubspot.mdx +++ b/src/provider-guides/hubspot.mdx @@ -58,15 +58,30 @@ The connector supports reading from: - [meeting-links](https://developers.hubspot.com/docs/api-reference/latest/scheduler/meetings/get-meeting-links) #### Event Occurrences -The connector reads HubSpot event occurrences (the [Events API](https://developers.hubspot.com/docs/api-reference/latest/events/retrieve-events/get-events)). -Connector exposes occurrences as separate *custom objects* whose names are constructed by combining a fixed *prefix* with the *event type* name. -* Naming rule: `AMPERSAND-event-occurrences-`: - * AMPERSAND-event-occurrences-e_call_ended - * AMPERSAND-event-occurrences-e_form_submission - * AMPERSAND-event-occurrences-e_mta_bounced_email_v2 - * AMPERSAND-event-occurrences-e_visited_page - -Where to get the event type name: event type identifiers are returned by the Events API's [event types endpoint](https://developers.hubspot.com/docs/api-reference/latest/events/retrieve-events/get-event-types). + +Event occurrences represent specific actions captured at a point in time, such as form submissions, email delivery, +sequence activity, and other **behavioral changes**. They are useful to understand when an event +happened and how that event may relate to automation or downstream workflows. + +To find the "event type" name, use the HubSpot Events API's +[list event types endpoint](https://developers.hubspot.com/docs/api-reference/latest/events/retrieve-events/get-event-types) +and [list custom event definitions](https://developers.hubspot.com/docs/api-reference/latest/events/define-events/create-event-definition). +Standard event type names begin with `e_`, while customer-specific custom event definitions use the `fullyQualifiedName` property with a `pe{HubId}_` prefix. +Standard events are safe to use across all customers, +while custom event definitions apply only to the specific customer account where they are defined. + +The HubSpot connector exposes event occurrences as **connector-defined objects** +named using the prefix `AMPERSAND-event-occurrences-` followed by the "event type" name. + + Note that **occurrences** is spelled with two c's and two r's, which is easy to miss. + + +Naming rule: `AMPERSAND-event-occurrences-`: +* AMPERSAND-event-occurrences-e_call_ended +* AMPERSAND-event-occurrences-e_form_submission +* AMPERSAND-event-occurrences-e_mta_bounced_email_v2 +* AMPERSAND-event-occurrences-e_visited_page +* AMPERSAND-event-occurrences-pe148543157_this_is_my_event #### Reading users and owners