Update task stages when software deployments complete
When a production deployment is tracked in ServiceNow, automatically move the associated feature task in Asana to the finished status.
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.
Asana Explore Asana →
TriggersFires when a new task or card is created in Asana.
Fires when a task in Asana is marked complete.
Fires when a task's due date in Asana is coming up.
Fires when a comment is added to a task in Asana.
Creates a new task in Asana.
Updates a task's status or assignee in Asana.
Posts a comment on a task in Asana.
Moves a task in Asana to a different board or list.
ServiceNow Explore ServiceNow →
TriggersFires when a new error or issue is captured in ServiceNow.
Fires when an issue's status changes in ServiceNow.
Fires when a new deployment is tracked in ServiceNow.
Creates or updates an issue in ServiceNow.
Assigns an issue in ServiceNow to a teammate.
Resolves or mutes an issue in ServiceNow.
More Asana + ServiceNow workflows
See all Asana + ServiceNow integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Update task stages when software deployments complete” between Asana and ServiceNow?
Yes — describe it in the box above and Knit's Integrations Agent researches Asana and ServiceNow'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 Developer Tools + Project Management automation?
Marking the linked task in Asana complete (or moving it to review) automatically when a pull request merges in ServiceNow.
Does this need commit messages to reference the task ID?
That's the most reliable way to match them, though the Agent can also match on branch name or a manually linked reference depending on your workflow.