Log developer issues from document status changes

When a specification document status changes in Stonly, automatically create an issue in Azure DevOps so engineers can start development.

Try:

See all Azure DevOps + Stonly integrations or talk to a human

Trusted by teams already building on Knit·

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.

Azure DevOps Explore Azure DevOps →

Triggers

Job completed

Fires when a job, build or file conversion finishes in Azure DevOps.

Job failed

Fires when a job, build or API request fails in Azure DevOps.

Actions

Run an API request

Calls an Azure DevOps endpoint with data from an earlier step.

Generate or convert a file

Creates a PDF, image or converted file with Azure DevOps.

Validate or look up a value

Checks or enriches a phone number, address or IP with Azure DevOps.

Stonly Explore Stonly →

Triggers

New page created

Fires when a new page or doc is created in Stonly.

Record added

Fires when a new record is added to a database or table in Stonly.

Doc published

Fires when a doc in Stonly is published or shared.

Status changed

Fires when a status field changes on a record in Stonly.

Actions

Create page from template

Starts a new page in Stonly from a saved template.

Add or update record

Creates or updates a record in Stonly.

Append text

Adds text to the end of an existing doc in Stonly.

Move page

Moves a page in Stonly into a different space.

Document tracked software deployments in wiki pages When a deployment is tracked in Azure DevOps, automatically append release details to the corresponding product page in Stonly. See details

Record captured software issues in central document tables When a new issue is captured in Azure DevOps, automatically add a record to the centralized bug database in Stonly. See details

See all Azure DevOps + Stonly integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Log developer issues from document status changes” between Azure DevOps and Stonly?

Yes — describe it in the box above and Knit's Integrations Agent researches Azure DevOps and Stonly'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 Azure DevOps to document tools in Stonly?

It automatically keeps release records and bug tables updated in Stonly while letting documentation status changes in Stonly generate software issues in Azure DevOps.

Can deployment updates in Azure DevOps update team documentation in Stonly?

Yes, whenever a deployment is tracked in Azure DevOps, release details can automatically append text to release documentation pages in Stonly.