Integrations

Both ways: what comes in, what goes back.

Stagewright doesn't only push content out. It reads your help center, support conversations, issues and analytics, maps them to features, and writes back verified articles, issues with video and verdicts on the PR.

Beta Every integration here is built and tested against the vendor's documented API. We're proving each one on live accounts with the first teams in the private beta.

Code hosts and CI

Where walkthroughs run on pull requests and the verdict is posted.

IntegrationReadsWritesConnects with
GitHubWalkthrough files and config at the PR's commit, changed files, preview deployment URLsThe Walkthroughs check with Approve, one sticky comment, a Stagewright Preview deployment, issuesThe Stagewright GitHub App (contents read-only), or stagewright ci in GitHub ActionsNot yet: GitHub Enterprise Server only through Actions
GitLabThe merge request's description and changesOne merge request note and a Walkthroughs commit statusstagewright ci in GitLab CI, gitlab.com and self-managed
Azure DevOpsThe pull request's description and changesOne PR thread and a status a branch policy can requirestagewright ci in Azure Pipelines, Services and Server
BitbucketThe pull request's description and changesOne PR comment and a Walkthroughs build statusstagewright ci in Bitbucket PipelinesNot yet: Bitbucket Data Center

Issue trackers

Regressions go out with their video; requests and fix proofs come back.

IntegrationReadsWritesConnects with
LinearDelegations and mentions (reproduce a bug, write a walkthrough, confirm a fix, is this covered?), status, commentsRegressions with the clip, frame, repro steps and trace; the PR author assigned; proven or not proven on the fixStagewright's Linear app, installed as an agent you can assign
JiraA request label or status, /stagewright comments, status, commentsRegressions with the video attached; a proven fix can move the issue to doneAtlassian OAuth (Jira Cloud)Not yet: Jira Data Center

Help centers and support

Articles and conversations are read back in and mapped to features; verified articles go back as drafts.

IntegrationReadsWritesConnects with
IntercomArticles, collections, conversations (kept as redacted question clusters)New and updated articles as drafts, with the video and the verified stampOAuth, or a pasted access token
ZendeskHelp Center articles and sections, tickets (kept as redacted question clusters)Draft articles; an update to a live article arrives as a linked draftOAuth, or an agent's API token
ProductlaneDocs articles and groups, threads (kept as redacted question clusters)Docs drafts in Productlane's review queue, or published articlesOAuth with PKCE, or a v2 API key

Product analytics

Usage events come in from the tools you already have and are mapped to features. Stagewright doesn't replace them.

IntegrationReadsWritesConnects with
PostHogEvents, imported on a schedule and mapped to features–PostHog export API with a project key
SegmentEvents through a Segment destination, hashed ids and allow-listed properties only–Segment destination with a publishable key

Coding agents

Your agents write and fix walkthroughs with the same tools you use.

IntegrationReadsWritesConnects with
Claude Code, Codex, CursorRepo scans, walkthroughs and courses written and validated, runs and their failure screensSkills, slash commands and the MCP serverThe Stagewright plugin (stagewright-ai/plugins), npx stagewright mcp, or the remote MCP server

Also

Webhooks for runs, approvals and publications (Standard Webhooks signing); an API with problem details and idempotency keys; Notion, Fireflies, Granola and Zoom as read-only sources for how your team explains the product, never quoted in a video. Slack isn't built yet.

Try it on your own product

Record a first walkthrough on your machine with no account. PR checks, approvals and publishing are in private beta: join the waitlist and we'll set you up by hand.