Workflows

Workflows are automation graphs. A workflow node can run tools and skills; an event bus can trigger workflows. There are three layers — templates (reusable definitions), instances (a template forked to a mission/project/ subject), and runs (one execution, with a per-node output log).

See the deep-dive in Authoring Workflows.

Use in the UI

Open Workflows under Settings (/workflows).

  • Build and edit workflow graphs; mark one as a template.
  • Fork a template to a mission/project/subject (an instance).
  • Watch runs execute with their per-node output.

Use with AI

  • workflows_create, workflows_update, workflows_delete / workflows_restore, workflows_list, workflows_get
  • workflows_instantiate — fork a template to a mission/project/subject
  • workflows_run, workflows_run_get, workflows_run_list, workflows_run_review, workflows_run_resume
  • events_emit, events_list — the event bus that can trigger workflows

The agent instantiates a template for a specific mission with workflows_instantiate, starts a run with workflows_run, and reads workflows_run_get output to decide next steps.

Use the API

curl https://<host>/api/invoke/workflows.list \
  -H "Authorization: Bearer $NIHMBUS_API_KEY"

Reference

Workflows (includes workflows.run*) · Workflow Events.