When new completed radar test run in Runscope, sync it to GitLab.
Update pipeline status or commit notes in GitLab when a Runscope Radar test run completes.
4.9/5 on G2·
Google for Startups Accelerator
How 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.
GitLab Explore GitLab →
TriggersFires when a job, build or file conversion finishes in GitLab.
Fires when a job, build or API request fails in GitLab.
Calls an GitLab endpoint with data from an earlier step.
Creates a PDF, image or converted file with GitLab.
Checks or enriches a phone number, address or IP with GitLab.
More Runscope + GitLab workflows
Open an issue for each new incident
When a new incident is opened in Runscope, create an issue in GitLab with the incident details.
See details
Mark deployments in monitoring
When a deployment finishes in GitLab, record it in Runscope so alerts can be read against it.
See details
Resolve incidents when the fix ships
When the linked issue is closed in GitLab, resolve the matching incident in Runscope.
See details
See all Runscope + GitLab integrations → · Browse the full workflow library →
Common questions
Can Knit build “When new completed radar test run in Runscope, sync it to GitLab.” between Runscope and GitLab?
Yes — describe it in the box above and Knit's Integrations Agent researches Runscope and GitLab'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 connect developer tools to a monitoring tool?
Most incidents follow a change. Linking GitLab and Runscope lets engineers see what was deployed around the time an alert fired, and turn an incident into tracked work.
Can an incident create an issue for the engineering team?
Yes. When an incident opens in Runscope, you can create an issue in GitLab so the fix is tracked alongside the code.