feat(self-driving): connect credential inbox sources via the secure connect link#238
Merged
Conversation
…ct link Credential-based connected tools (Zendesk, pganalyze, Jira) were armed as dormant responders and never actually connected in-run, because the flow refused to collect API credentials. Reuse the existing connect-link handoff instead: hand the user a secure PostHog connect page, wait for them to store credentials in the browser (never in chat), then create the live source from the stored credential via data-warehouse-source-setup. Dormant + follow-up is now only the fallback when the user skips or can't finish.
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
…rces Switch the credential connector from data-warehouse-source-setup (which enables every discoverable table) to external-data-sources-create with an explicit single-table schema, matching the Linear connector. Credential inbox sources now sync just their actionable table (tickets/issues) via the stored credential. Depends on the posthog create endpoint accepting a credential_id; degrades to the dormant fallback on older backends.
Merged
2 tasks
Member
Author
|
The single-table behavior here depends on PostHog/posthog#71056 (create endpoint accepting a stored credential_id). Deploy that first for one-table syncs; on an older backend the connector degrades gracefully to the dormant-responder fallback. |
danielcarletti
approved these changes
Jul 15, 2026
andrewm4894
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Builds on #237 (now merged, which added Jira as a connected-tool inbox source). This PR connects API-credential sources for real, instead of arming dormant responders.
Zendesk, pganalyze, and Jira authenticate with API credentials, and the self-driving flow previously refused to collect them in-run, so it just enabled a dormant responder (a signal toggle with no warehouse source behind it) and left a follow-up. The responder stayed silent until the user separately went and connected the source.
The fix
Reuse the existing connect-link handoff that already backs agent-driven source setup. For any API-credential tool the user picks, the self-driving run now:
data-warehouse-source-connect-linkto get a secure PostHog connect URL,data-warehouse-stored-credentials-list,data-warehouse-source-setupwith{ "credential_id": ... }.Dormant responder + follow-up is now only the fallback when the user skips or can't finish, the same posture the Linear connector already uses when its OAuth grant doesn't land.
Changes
references/5c-credentials.md(mirrors5b-linear.md, but the "one click" is entering credentials on the connect page).references/5-connected-tools.md— dispatch credential sources to the new connector; reframe the intro and class-recording language.description.md— the per-source connector confirms (now including the credential connect links) can't be batched.Context
No backend or wizard code needed. The connect object model (
PendingSourceCredential), the connect page (/data-warehouse/connect?kind=X), and all three MCP tools already exist and ship today. This only teaches the self-driving flow to use them. Verified the skill bundle rebuilds and carries the connect-link flow.