feat(self-driving): connect credential inbox sources via the secure connect link#237
Merged
Merged
Conversation
Jira's warehouse source authenticates with an Atlassian API token (not the kind=jira OAuth integration), so the run can't auto-connect it in-flight. Treat it like Zendesk/pganalyze: arm the dormant jira/issue responder and record a follow-up. The backend signals emitter and inbox UI already ship.
🧙 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. |
Gilbert09
changed the title
Member
Author
|
Correction: this PR is merged (I misread it as sync-stuck). Follow-up #238 builds the connect-link handoff on top of it. |
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
1 participant
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
Two related changes to the self-driving setup skill's connected-tool step:
jira/issueresponder mapping, already-connected detection).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.