Track recurring alerts
When the same monitor alerts again in ilert, add a comment to its existing task in Asana.
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.
ilert Explore ilert →
TriggersFires when a monitor or check in ilert raises an alert.
Fires when an incident is opened or updated in ilert.
Fires when a monitored site, service or alarm in ilert changes state.
Opens a new incident or alert in ilert.
Acknowledges an open incident in ilert.
Resolves an incident in ilert.
Asana Explore Asana →
TriggersFires when a new task, job or item 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 task, job or project changes status in Asana.
Creates a new task, job or item in Asana.
Updates a task's status or assignee in Asana.
Posts a comment on a task in Asana.
Assigns a task in Asana to a team member.
More ilert + Asana workflows
See all ilert + Asana integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Track recurring alerts” between ilert and Asana?
Yes — describe it in the box above and Knit's Integrations Agent researches ilert and Asana'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 send incidents to a project management tool?
The alert is handled in ilert, but the follow-up work lives in Asana. Creating tasks automatically keeps that work visible and assigned.
Can I track action items from each incident?
Yes. When an incident is resolved in ilert, create a task in Asana for the review and any follow-up actions.