How do I document a provisioning process as a workflow?

Requires Elite

Quick answer

On the Workflows tab of the Provisioning area, you document the process of a rollout: Name, Type (Provisioning or Deprovisioning), the Steps in order, and optionally the Script path of the associated automation script. This way, the whole team can follow exactly how a system is set up — and torn down again.

Prerequisites

Provisioning is available from the Elite tier.

Open the “Workflows” tab. Choose Provisioning and switch to the Workflows tab. The table shows existing workflows with their name, type and script path.

Screenshot pending provisioning-ablauf-01 Workflows tab in the Provisioning area with the 'Add Workflow' dialog

A workflow with steps and a script path.
Create a workflow. Click “Add Workflow” and fill in the dialog:
- Name (required) — e.g. “New webserver (standard)”.
- Type (required) — Provisioning or Deprovisioning.
- Steps — the process in order, one step per line, e.g.:
  Example steps
```
1. VM aus Basis-Image klonen
2. IP aus dem Netzwerk-Modul reservieren
3. Vorlage 'Nginx vHost Standard' rendern und ausrollen
4. System ins Monitoring aufnehmen
5. Asset in Notory anlegen und verknüpfen
```
- Script path (optional) — path/repo of the automation script, e.g. ansible/playbooks/webserver.yml.
- Description (optional).
Save. The workflow appears in the list and now serves as the authoritative process documentation.

Create a workflow — POST /api/v1/provisioning/workflows (scope write):

curl -X POST https://demo.notory.io/api/v1/provisioning/workflows \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Neuer Webserver (Standard)",
    "workflow_type": "provisioning",
    "steps": "1. VM klonen\n2. IP reservieren\n3. Vorlage rendern\n4. Monitoring aufnehmen\n5. Asset anlegen",
    "script_path": "ansible/playbooks/webserver.yml",
    "description": "Standardablauf für neue Webserver"
  }'

{
  "id": "wf_2b3c…",
  "tenant_id": "3d9b0c12-…",
  "name": "Neuer Webserver (Standard)",
  "workflow_type": "provisioning",
  "steps": "1. VM klonen\n2. IP reservieren\n3. Vorlage rendern\n4. Monitoring aufnehmen\n5. Asset anlegen",
  "script_path": "ansible/playbooks/webserver.yml",
  "description": "Standardablauf für neue Webserver",
  "created_at": "2026-07-08T11:30:00Z",
  "updated_at": "2026-07-08T11:30:00Z"
}

List with GET /api/v1/provisioning/workflows, change via PUT, delete via DELETE (administrators only).

Possible errors: 401, 403 (Provisioning is not in your tier or no write access), 404 (workflow not found), 422 (validation).

What happens behind the scenes?

Documentation, not execution: Notory does not execute workflows — they are the authoritative, versioned description of the process. The referenced script (script path) runs in your own automation (e.g. Ansible, CI).
Interplay between modules: A typical process references templates (generate a configuration), the network module (reserve an IP), monitoring (enroll the system), and assets (maintain the inventory).
Tenant isolation & audit: Workflows belong to your tenant; every change is logged.