Document tracked software deployments in wiki pages
When a deployment is tracked in GitHub, automatically append release details to the corresponding product page in XRay Workflow.
See all XRay Workflow + GitHub integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
XRay Workflow Explore XRay Workflow →
TriggersFires when a new page or doc is created in XRay Workflow.
Fires when a new record is added to a database or table in XRay Workflow.
Fires when a doc in XRay Workflow is published or shared.
Fires when a status field changes on a record in XRay Workflow.
Starts a new page in XRay Workflow from a saved template.
Creates or updates a record in XRay Workflow.
Adds text to the end of an existing doc in XRay Workflow.
Moves a page in XRay Workflow into a different space.
GitHub Explore GitHub →
TriggersFires when a job, build or file conversion finishes in GitHub.
Fires when a job, build or API request fails in GitHub.
Calls an GitHub endpoint with data from an earlier step.
Creates a PDF, image or converted file with GitHub.
Checks or enriches a phone number, address or IP with GitHub.
More XRay Workflow + GitHub workflows
Record captured software issues in central document tables
When a new issue is captured in GitHub, automatically add a record to the centralized bug database in XRay Workflow.
See details
Log developer issues from document status changes
When a specification document status changes in XRay Workflow, automatically create an issue in GitHub so engineers can start development.
See details
See all XRay Workflow + GitHub integrations → · Browse the full workflow library →
Common questions
Can Knit build “Document tracked software deployments in wiki pages” between XRay Workflow and GitHub?
Yes — describe it in the box above and Knit's Integrations Agent researches XRay Workflow and GitHub's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why connect development platforms in GitHub to document tools in XRay Workflow?
It automatically keeps release records and bug tables updated in XRay Workflow while letting documentation status changes in XRay Workflow generate software issues in GitHub.
Can deployment updates in GitHub update team documentation in XRay Workflow?
Yes, whenever a deployment is tracked in GitHub, release details can automatically append text to release documentation pages in XRay Workflow.