docs(hubspot): document Enroll in Sequence and Retrieve enrollment status actions

[george-dilthey]

What changed

Added two previously undocumented HubSpot sequence actions to docs/hubspot-integration-overview.md:

1. Action Enroll a contact in a sequence — documents inputs (Contact ID, Sequence, Sender email, optional Sender alias address), the prerequisite that sequences OAuth scopes must be enabled, and a note explaining that sender identity is determined by the connection owner's HubSpot account.

2. Action Retrieve enrollment status of a contact — documents the single input (Contact ID) and what the action does.

Also added a new FAQ: "Why does each team member need their own HubSpot connection to enroll contacts in sequences?" This explains that HubSpot derives sender identity from the OAuth token (not the Clay user), so each sender needs their own connection — and clarifies that the Enterprise connection-sharing feature (Settings → Connections) allows other members to configure the action but still sends from the connection owner's HubSpot inbox.

Why

An Ops user at Quandri (Intercom conversation 215475011543062, tagged "HubSpot – Sequencer Push") asked: "Why can't I enrol people into a HubSpot sequence for other users?" They clarified: "It says to connect the mailbox. The mailbox is connect to another user not mine directly."

Fin gave a partially correct answer (share the connection via Settings → Connections, or connect your own account) but missed two key nuances: (1) the connection-sharing feature is Enterprise-only, and (2) even sharing a connection doesn't change the sender identity — enrollments always come from the connection owner's HubSpot inbox.

The root gap: neither the "Enroll a contact in a sequence" nor the "Retrieve enrollment status of a contact" actions were documented anywhere in hubspot-integration-overview.md, despite both actions existing in public-actions/apps/hubspot-new-ui/actions/hubspot-enroll-contact/ and hubspot-get-enrollment-status/ respectively.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/_/inbox/conversation/215475011543062
• Code: public-actions/apps/hubspot-new-ui/actions/hubspot-enroll-contact/action-code.ts:40 — getUserIDFromAccessToken confirms sender identity comes from the OAuth token
• Code: public-actions/apps/hubspot-new-ui/actions/hubspot-enroll-contact/input-parameter-schema.ts — confirms all four inputs (contactId, sequenceId, senderEmail, senderAliasAddress)
• Verifier: Enterprise-only gate confirmed via clay-base/libs/shared/src/billing/plan.ts:318 (EnableAppAccountAccessSettings: true only in ENTERPRISE_PLAN_DEFAULT_FEATURE_FLAGS)
• Verifier Slack context: #team-product-support thread (2026-02-27) confirms per-SDR connection requirement; #ent-atomic-clay (2026-06-10) confirms connection owner's HubSpot user ID is used for enrollment

Uncertainties

None — both action schemas and the sender-identity behavior are directly confirmed by code. The Enterprise-only gate on connection access sharing is confirmed by the verifier against the billing plan constants.

Related observations

• The access-settings-for-connections.md doc already correctly states the feature is Enterprise-only, so no changes needed there.
• The existing sequences-scopes authorization FAQ (Why do I get "Authorization failed...") is accurate and was left unchanged.

Closes DOC-1083

[linear-code]

DOC-1083