Announce resolution
When an incident is resolved in Urlooker, post an all-clear message in Discord.
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.
Urlooker Explore Urlooker →
TriggersFires when a monitor or check in Urlooker raises an alert.
Fires when an incident is opened or updated in Urlooker.
Fires when a monitored site, service or alarm in Urlooker changes state.
Opens a new incident or alert in Urlooker.
Acknowledges an open incident in Urlooker.
Resolves an incident in Urlooker.
Discord Explore Discord →
TriggersFires when a new message is posted to a channel in Discord.
Fires when your team or a keyword is mentioned in Discord.
Fires when a new channel is created in Discord.
Fires when a new file is shared in Discord.
Posts a message to a channel in Discord.
Sends a direct message to a person in Discord.
Creates a new channel in Discord.
Adds a user to a channel in Discord.
More Urlooker + Discord workflows
See all Urlooker + Discord integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Announce resolution” between Urlooker and Discord?
Yes — describe it in the box above and Knit's Integrations Agent researches Urlooker and Discord'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 post monitoring alerts to team chat?
Engineers already work in Discord. Posting Urlooker alerts there means problems are seen quickly and the discussion happens alongside the alert.
Can I route alerts to different channels?
Yes. Send alerts from Urlooker to different Discord channels based on the service, monitor or severity.