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