> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ntropii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started

> Define a workflow for your business process — either pick a template from runbook-templates or build a new runbook from scratch.

A **workflow** is a binding of a **runbook** (the deterministic Python templates that drive the process) to an **entity**, optionally on a schedule. A runbook may invoke external **agents** (Claude Managed, Copilot, …) from inside its steps when it needs LLM-driven artefact generation that doesn't fit the deterministic capabilities surface.

There are two paths to a working workflow on Ntropii:

<CardGroup cols={2}>
  <Card title="Pick a template" icon="folder-tree" href="https://github.com/ntropii-com/runbook-templates">
    Start from a runbook in [`runbook-templates`](https://github.com/ntropii-com/runbook-templates). Today: `nav-monthly`, `nav-monthly-journals`, `document-ingest`, `expense-processor`. Configure for your tenant + entity and deploy.
  </Card>

  <Card title="Build a new runbook" icon="hammer" href="/workflows/runbooks/overview">
    When no template fits, author a new runbook from scratch — `@runbook.defn` class, `@runbook.step` methods, HITL gates. The platform's coding-agent assistant can scaffold from a skill definition.
  </Card>
</CardGroup>

## Deploying a workflow

Either path lands at the same `ntro workflow create --path` flow. The CLI uploads the runbook bundle, binds it to an entity, and (optionally) attaches a schedule:

```bash theme={null}
# Deploy a template runbook
ntro workflow create \
  --path ./runbooks/nav-monthly/ \
  --tenant acme-fund-admin \
  --entity acme-commercial-spv1 \
  --schedule "0 8 5 * *"

# Deploy a runbook from a different path under a second tenant
ntro workflow create \
  --path ./runbooks/nav-monthly/ \
  --tenant beta-fund-admin \
  --entity beta-spv1
```

Behind the scenes, the workflow is created with `runbookSlug` (the deployed code identifier) + `entityId` (where it operates) + an optional schedule. The same runbook can be deployed under multiple tenants — each deployment becomes a separate workflow.

## Importing an agent

If your workflow needs a step that generates a complex artefact (auditor handover .docx, narrative summary, etc.), register an external agent and invoke it from inside a runbook step. See [Register agents](/workflows/agents/register).

## Next steps

<CardGroup cols={2}>
  <Card title="Build runbooks" icon="code" href="/workflows/runbooks/overview">
    Concept walkthrough: `NtroWorkflow`, `@runbook.step`, HITL gates, child workflows.
  </Card>

  <Card title="Skill definitions" icon="brain" href="/workflows/runbooks/skill-definitions">
    The runbook.md / skill.md frontmatter the platform's coding-agent assistant uses to scaffold a workflow.
  </Card>

  <Card title="Register agents" icon="server-cog" href="/workflows/agents/register">
    Bring an external agent (Claude Managed, Copilot) into a runbook step.
  </Card>

  <Card title="Deploy to production" icon="rocket" href="/deploy-and-run/deploy-to-production">
    Push runbooks at versioned paths; pin versions per tenant.
  </Card>
</CardGroup>