Update ticket status when documentation status changes
When a document's status changes in Stonly, automatically update the corresponding ticket status in SolarWinds Service Desk to reflect progress.
See all SolarWinds Service Desk + Stonly 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.
SolarWinds Service Desk Explore SolarWinds Service Desk →
TriggersFires when a new support ticket or chat conversation starts in SolarWinds Service Desk.
Fires when a ticket's status changes in SolarWinds Service Desk.
Fires when a ticket in SolarWinds Service Desk is assigned to an agent.
Fires when a ticket in SolarWinds Service Desk breaches its response SLA.
Creates a new ticket in SolarWinds Service Desk.
Updates a ticket's status in SolarWinds Service Desk.
Assigns a ticket in SolarWinds Service Desk to an agent.
Posts a reply or internal note on a ticket or conversation in SolarWinds Service Desk.
Stonly Explore Stonly →
TriggersFires when a new page or doc is created in Stonly.
Fires when a new record is added to a database or table in Stonly.
Fires when a doc in Stonly is published or shared.
Fires when a status field changes on a record in Stonly.
Starts a new page in Stonly from a saved template.
Creates or updates a record in Stonly.
Adds text to the end of an existing doc in Stonly.
Moves a page in Stonly into a different space.
More SolarWinds Service Desk + Stonly workflows
Log ticket SLA breaches into incident docs
When an SLA is breached in SolarWinds Service Desk, automatically append the breach details to your incident log page in Stonly for team post-mortems.
See details
Create support tickets from published documentation
When a new page is created in Stonly, automatically create a tracking ticket in SolarWinds Service Desk so team members can review and approve it.
See details
See all SolarWinds Service Desk + Stonly integrations → · Browse the full workflow library →
Common questions
Can Knit build “Update ticket status when documentation status changes” between SolarWinds Service Desk and Stonly?
Yes — describe it in the box above and Knit's Integrations Agent researches SolarWinds Service Desk 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 pair Stonly and SolarWinds Service Desk?
Connecting these apps bridges support operations and knowledge management, allowing support tickets and team documentation to stay synchronized effortlessly.
Can SLA warnings in SolarWinds Service Desk alert our team inside Stonly?
When an SLA is breached in SolarWinds Service Desk, you can automatically append warning details or update project records in Stonly to escalate the issue.