When new event in Hexowatch, sync it to Cryptolens.
When a new event occurs in Hexowatch, update license tracking in Cryptolens.
See all Cryptolens + Hexowatch integrations or talk to a human
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.
Cryptolens Explore Cryptolens →
TriggersFires when a job, build or file conversion finishes in Cryptolens.
Fires when a job, build or API request fails in Cryptolens.
Calls an Cryptolens endpoint with data from an earlier step.
Creates a PDF, image or converted file with Cryptolens.
Checks or enriches a phone number, address or IP with Cryptolens.
Hexowatch Explore Hexowatch →
TriggersFires when a monitor or check in Hexowatch raises an alert.
Fires when an incident is opened or updated in Hexowatch.
Fires when a monitored site, service or alarm in Hexowatch changes state.
Opens a new incident or alert in Hexowatch.
Acknowledges an open incident in Hexowatch.
Resolves an incident in Hexowatch.
More Cryptolens + Hexowatch workflows
Open an issue for each new incident
When a new incident is opened in Hexowatch, create an issue in Cryptolens with the incident details.
See details
Mark deployments in monitoring
When a deployment finishes in Cryptolens, record it in Hexowatch so alerts can be read against it.
See details
Resolve incidents when the fix ships
When the linked issue is closed in Cryptolens, resolve the matching incident in Hexowatch.
See details
See all Cryptolens + Hexowatch integrations → · Browse the full workflow library →
Common questions
Can Knit build “When new event in Hexowatch, sync it to Cryptolens.” between Cryptolens and Hexowatch?
Yes — describe it in the box above and Knit's Integrations Agent researches Cryptolens and Hexowatch'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 Cryptolens and Hexowatch 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 Hexowatch, you can create an issue in Cryptolens so the fix is tracked alongside the code.