Build developer tools workflows between Cortex and Jenkins on a visual canvas — map fields once and let data flow.
Example: when Jenkins's "Watch New Builds" fires, WEXTL can "Delete Analyzer" in Cortex. Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer); Jenkins has 64 actions (including Add Job to View, Build Job, and Build Job With Parameters).
Common questions about connecting Cortex and Jenkins.