Getting started

Use Norevin from zero to your first monitored workflow.

A practical first-run guide for creating your workspace, connecting one automation tool, sending your first checkpoint, and knowing what to check next.

Start small

One workflow is enough to learn the whole product.

The fastest path is to monitor one workflow from start to finish. Once the first checkpoint appears in Norevin, you can add more checkpoints, AI validation, alerts, and reports without changing the basic connection pattern.

Start freeConnect a tool
Step 1

Set up the workspace around one real workflow.

These four items create the minimum useful Norevin setup: a client, a workflow, checkpoint names, and a scoped connection key.

1

Pick one workflow

Start with one real automation that matters to a client or business outcome, such as lead intake, quote follow-up, support triage, or weekly reporting.

Write down the final outcome first. Norevin is most useful when it can prove the workflow reached that outcome.Create workspace
2

Create a client

In the console, add the client or internal team that owns the workflow. This keeps incidents, reports, and keys scoped to the right account.

For internal operations, the client can be your own company or team.Open clients
3

Create a workflow

Name the workflow and add the checkpoints you expect to happen in order.

Good first checkpoints are lead_received, ai_classified, crm_updated, and email_sent. Use names your team can recognize in logs.Open workflows
4

Create a connection key

Generate a scoped key for the workflow. Use events:write for checkpoints and validations:write when you also validate AI output.

Keep the key in your automation tool's secret storage. Do not paste raw keys into tickets, docs, screenshots, or support email.Open API keys
Step 2

Connect the automation tool you already use.

Norevin receives normal HTTPS requests. The tool changes, but the pattern stays the same: POST JSON, send the Bearer key, reuse one run_id per automation run.

n8n

  1. Add an HTTP Request node after the workflow step you want to monitor.
  2. Set Method to POST and URL to https://norevin.com/api/checkpoint.
  3. Add Authorization: Bearer <NOREVIN_API_KEY> and Content-Type: application/json.
  4. Use the n8n execution id as run_id and reuse it for every checkpoint in the same run.

Make

  1. Add an HTTP module after the important scenario step.
  2. Set the request body to raw JSON and paste the checkpoint payload.
  3. Use the same scenario execution identifier as run_id across all checkpoint modules.
  4. Set is_final to true only on the last successful checkpoint in the scenario.

Zapier

  1. Use Webhooks by Zapier with Custom Request.
  2. Choose POST, add the Norevin endpoint, and send JSON data.
  3. Store the API key in Zapier's secure fields and send it as a Bearer token.
  4. Use the same run_id for every checkpoint created by one Zap execution.

Custom HTTP

  1. Send a POST request from your app, worker, or automation script.
  2. Use Authorization: Bearer <NOREVIN_API_KEY>.
  3. Retry safely with the same idempotency_key when the network fails.
  4. Send failed or skipped status explicitly when the workflow branch does not finish.
Step 3

Send checkpoints and optional AI validation.

Use these examples to understand the shape of the request. In the logged-in Templates page, Norevin fills in your real workflow id, checkpoint names, and schema names.

POST

/api/checkpoint

Call this after a workflow step succeeds, fails, or is skipped.

{
  "workflow_id": "00000000-0000-0000-0000-000000000000",
  "run_id": "automation-run-123",
  "checkpoint": "crm_updated",
  "status": "success",
  "idempotency_key": "automation-run-123:crm_updated",
  "is_final": true,
  "platform": "n8n",
  "metadata": {
    "source": "lead intake",
    "workflow": "New lead to CRM"
  },
  "payload_summary": {
    "records_processed": 1
  }
}
POST

/api/validate

Call this after an AI step returns structured output.

{
  "workflow_id": "00000000-0000-0000-0000-000000000000",
  "schema_name": "Lead classification",
  "run_id": "automation-run-123",
  "idempotency_key": "automation-run-123:Lead classification",
  "output": {
    "category": "qualified",
    "confidence": 0.91,
    "next_step": "book_call"
  }
}
Step 4

Operate the workflow after the first signal arrives.

Once Norevin receives data, use the console to check runs, resolve incidents, turn on alert channels, and create reports for clients or internal stakeholders.

Send the first checkpoint

Use the Templates page to generate a request with your real workflow id and checkpoint names, then send one test signal.

Open templates

Add AI Output Guard

Create a validation schema for AI-generated JSON, then call /api/validate after the AI step returns structured output.

Open validations

Turn on alerts

Add email or Slack alert channels so missing checkpoints and failed validations reach the right person.

Open alerts

Read incidents and reports

Use incidents to fix broken runs, then generate a sanitized client-facing report once the workflow has useful data.

Open reports
Step 5

Know when the first workflow is actually connected.

Before adding more clients or workflows, confirm this checklist. It keeps setup honest and gives support enough detail to help quickly.

  • One client exists.
  • One workflow has clear checkpoint names.
  • One scoped API key exists and is stored only in the automation tool.
  • At least one checkpoint request returns ok: true.
  • Runs and events appear in the Norevin dashboard.
  • Alerts point to a real inbox or Slack destination.
  • A report can be generated without exposing raw secrets or full payloads.
Need the generated requests?

The logged-in Templates page turns this guide into copy-ready setup.

Choose your platform, workflow, checkpoint, and validation schema. Norevin will generate request bodies with your real ids so you do not have to assemble them by hand.

Open templates