Skip to content

feat(data-warehouse): wire Intercom and HubSpot into the self-driving inbox#3614

Open
Gilbert09 wants to merge 1 commit into
mainfrom
tom/inbox-oauth-wiring
Open

feat(data-warehouse): wire Intercom and HubSpot into the self-driving inbox#3614
Gilbert09 wants to merge 1 commit into
mainfrom
tom/inbox-oauth-wiring

Conversation

@Gilbert09

Copy link
Copy Markdown
Member

Problem

Intercom and HubSpot are the two OAuth-connected support sources deferred from the initial
30-source inbox batch (#3597). With the generic OAuth flow starter in place
(#3613), they can be wired in like any other source.

Changes

Two entries in the shared EXTERNAL_INBOX_SOURCES registry (setup: "dynamic"), plus the
matching SourceProduct/ToggleableSourceProduct, SignalSourceConfig.source_product, and
analytics-event unions, and their icon metadata. No bespoke setup form: DynamicSourceSetup
renders each source's oauth field generically and the generic integration router starts the
flow by kind.

How did you test this?

  • turbo typecheck for @posthog/ui, @posthog/core, @posthog/shared, @posthog/api-client,
    @posthog/mobile — pass.
  • pnpm --filter @posthog/shared build; biome check on changed files — clean.

Dependencies

@github-actions

github-actions Bot commented Jul 21, 2026

Copy link
Copy Markdown

React Doctor found no issues in the changed files. 🎉

Reviewed by React Doctor for commit 7dfedac.

Base automatically changed from tom/inbox-tier1-sources to main July 21, 2026 17:06
@trunk-io

trunk-io Bot commented Jul 21, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

… inbox

Add Intercom and HubSpot as inbox source toggles. Both are OAuth sources,
but that needs no bespoke UI: the generic DynamicSourceSetup renders their
connect form's oauth field, and the generic integration flow starter
(separate PR) launches the OAuth flow by kind. So this is the same
one-registry-entry change as any credential source — two entries in
EXTERNAL_INBOX_SOURCES plus the SourceProduct/analytics unions and icons.
@Gilbert09
Gilbert09 force-pushed the tom/inbox-oauth-wiring branch from 97614bd to 7dfedac Compare July 21, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant