OCNORA
Solutions · IT operations

Runbooks that run themselves, and tell you when they didn’t.

Health checks, onboarding, ticket routing and alert handling as workflows you can read, with an ops center that separates “not running” from “broken”.

What you automate

Three workflows teams build here first.

  1. 01

    Scheduled health checks that page the right person and open a ticket only when the retry also fails.

  2. 02

    Joiner, mover, leaver flows across identity, chat, ticketing and cloud accounts.

  3. 03

    Alert enrichment: pull the log line, the owner and the last deploy before a human ever reads the page.

From the template library

Scheduled health check with email alert

Ping an endpoint every 5 minutes; if it does not return 200, email the on-call address with the status code.

A scheduled HTTP check that branches on the status code and only emails when the endpoint is unhealthy.5 nodes · about 5 min to set up
Why OCNORA here

Built for this, not adapted to it.

85 trigger types

Schedules, webhooks, queues, mailboxes and app events, so a runbook starts from whatever already happens in your stack.

Cloud services as nodes

394 AWS, 182 Azure and 152 Google Cloud services are in the catalog as typed nodes with the provider’s own auth. No SDK glue.

HTTP node with cURL import

Paste the cURL from a vendor’s docs and get a configured request node. Anything with an API is reachable in one step.

Error workflows and retries

Per-step retries and timeouts, and a separate error workflow that runs when the main one fails, so the failure itself is handled by a workflow.

Workflow Health before the first run

Missing connections, unreachable hosts and bad expressions are caught by a health pass before the schedule fires, and Auto Fix repairs what it safely can.

An ops center, not a list

Status and health are separate columns. An attention tab shows what needs a human now; the failure drawer shows the run, the step and the payload.

Integrations

Apps this kind of workflow usually touches.

Each one has its own page with operations, triggers and auth.

See a workflow run in your first ten minutes.

Create a workspace, import an n8n file or start from a template, and watch Workflow Health check it before it ever runs.