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