Open an issue for each new incident

When a new incident is opened in Runscope, create an issue in Amazon SQS with the incident details.

Try:

See all Runscope + Amazon SQS integrations or talk to a human

Trusted by teams already building on Knit·

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 →

Triggers

New alert

Fires when a monitor or check in Runscope raises an alert.

New or updated incident

Fires when an incident is opened or updated in Runscope.

Monitor state changed

Fires when a monitored site, service or alarm in Runscope changes state.

Actions

Create incident

Opens a new incident or alert in Runscope.

Acknowledge incident

Acknowledges an open incident in Runscope.

Resolve incident

Resolves an incident in Runscope.

Amazon SQS Explore Amazon SQS →

Triggers

Job completed

Fires when a job, build or file conversion finishes in Amazon SQS.

Job failed

Fires when a job, build or API request fails in Amazon SQS.

Actions

Run an API request

Calls an Amazon SQS endpoint with data from an earlier step.

Generate or convert a file

Creates a PDF, image or converted file with Amazon SQS.

Validate or look up a value

Checks or enriches a phone number, address or IP with Amazon SQS.

Mark deployments in monitoring When a deployment finishes in Amazon SQS, 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 Amazon SQS, resolve the matching incident in Runscope. See details

See all Runscope + Amazon SQS integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Open an issue for each new incident” between Runscope and Amazon SQS?

Yes — describe it in the box above and Knit's Integrations Agent researches Runscope and Amazon SQS'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 Amazon SQS 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 Amazon SQS so the fix is tracked alongside the code.