IT OPS

On-Demand Single-Host Compliance Check via Webhook

Accepts a hostname over an HTTP webhook, runs the shell encryption and patch probe against just that machine, and replies with a pass/fail verdict plus the details inline.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook receives target hostnameHTTP webhook
  • LogicValidate hostname is known and well-formed
  • ActionShell probe scoped to the single hostShell
  • LogicFold fields into pass/fail verdict with reasons
  • OutputReturn verdict and detail in response bodyHTTP webhook

What it does

This workflow exposes the compliance probe as an on-demand API. Send it a hostname and it runs the shell checks against that single endpoint, then returns a structured verdict — encrypted yes/no, patch age, and an overall pass/fail — directly in the webhook response. No board, no channel, just an answer.

When to use it

Use it inside other tooling: a help-desk macro, a device-onboarding gate, or a chatbot command where an agent needs to confirm one machine's state right now. It is the building block other compliance flows can call.

How it works

  1. 1An HTTP webhook receives a request carrying the target hostname.
  2. 2A logic step validates the hostname is known and well-formed, rejecting bad input.
  3. 3A shell step runs the encryption and patch probe scoped to that one host.
  4. 4A logic step folds the raw fields into a single pass/fail verdict with reasons.
  5. 5The output returns the verdict and detail JSON in the webhook response body.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ShellRun sandboxed commands inside the workspace.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.