Post new alerts to a channel
When Updown.io raises a new alert, post it to the team's channel in Flock.
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.
Flock Explore Flock →
TriggersFires when a new message is posted to a channel in Flock.
Fires when your team or a keyword is mentioned in Flock.
Fires when a new channel is created in Flock.
Fires when a new file is shared in Flock.
Posts a message to a channel in Flock.
Sends a direct message to a person in Flock.
Creates a new channel in Flock.
Adds a user to a channel in Flock.
Updown.io Explore Updown.io →
TriggersFires when a monitor or check in Updown.io raises an alert.
Fires when an incident is opened or updated in Updown.io.
Fires when a monitored site, service or alarm in Updown.io changes state.
Opens a new incident or alert in Updown.io.
Acknowledges an open incident in Updown.io.
Resolves an incident in Updown.io.
More Flock + Updown.io workflows
See all Flock + Updown.io integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Post new alerts to a channel” between Flock and Updown.io?
Yes — describe it in the box above and Knit's Integrations Agent researches Flock and Updown.io'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 Flock. Posting Updown.io 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 Updown.io to different Flock channels based on the service, monitor or severity.