Resolve incidents when the fix ships
When the linked issue is closed in AWS Lambda, resolve the matching incident in Runscope.
See all Runscope + AWS Lambda integrations or talk to a human
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.
AWS Lambda Explore AWS Lambda →
TriggersFires when a job, build or file conversion finishes in AWS Lambda.
Fires when a job, build or API request fails in AWS Lambda.
Calls an AWS Lambda endpoint with data from an earlier step.
Creates a PDF, image or converted file with AWS Lambda.
Checks or enriches a phone number, address or IP with AWS Lambda.
More Runscope + AWS Lambda workflows
See all Runscope + AWS Lambda integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Resolve incidents when the fix ships” between Runscope and AWS Lambda?
Yes — describe it in the box above and Knit's Integrations Agent researches Runscope and AWS Lambda'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 AWS Lambda 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 AWS Lambda so the fix is tracked alongside the code.