Resolve customer tickets automatically when tasks complete
When an engineer marks a bug fix task as complete in Microsoft To Do, update the status of the related support ticket in SolarWinds Service Desk so support can notify the customer.
See all SolarWinds Service Desk + Microsoft To Do integrations or talk to a human
Google for Startups AcceleratorHow 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.
Microsoft To Do Explore Microsoft To Do →
TriggersFires when a new task, job or item is created in Microsoft To Do.
Fires when a task in Microsoft To Do is marked complete.
Fires when a task's due date in Microsoft To Do is coming up.
Fires when a task, job or project changes status in Microsoft To Do.
Creates a new task, job or item in Microsoft To Do.
Updates a task's status or assignee in Microsoft To Do.
Posts a comment on a task in Microsoft To Do.
Assigns a task in Microsoft To Do to a team member.
More SolarWinds Service Desk + Microsoft To Do workflows
See all SolarWinds Service Desk + Microsoft To Do integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Resolve customer tickets automatically when tasks complete” between SolarWinds Service Desk and Microsoft To Do?
Yes — describe it in the box above and Knit's Integrations Agent researches SolarWinds Service Desk and Microsoft To Do'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.
What's the most common Project Management + Ticketing automation?
Creating a task in Microsoft To Do whenever a ticket in SolarWinds Service Desk is escalated or tagged as a bug, with a two-way status sync so support sees engineering progress without leaving SolarWinds Service Desk.
Can status updates flow back to the original ticket?
Yes — when the linked task in Microsoft To Do changes status, the Agent can post that update back onto the original ticket in SolarWinds Service Desk automatically.