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

# Quickstart

Create, test, publish, and observe your first B3OS workflow.

This guide walks through the shortest path from a new organization to a published workflow. You can build in the B3OS web app or call the REST API directly.



**Start in the app unless you are automating setup**

The visual editor is the fastest way to learn B3OS because it validates triggers, action schemas, connector
  requirements, expressions, and test runs in context.

Your browser does not support the video element.

## Create a Workflow

**Open or create an organization**

Sign in to B3OS, create an organization, and invite teammates only after you have the first workflow running.
  **Create a workflow draft**

Choose a blank workflow, a template, or a Caddie-assisted starting point. Drafts are editable without changing the live version.
  **Choose a trigger**

Use **Manual** for a first test, **Schedule** for recurring automation, or a connector/event trigger when you are wiring B3OS to an external system.
  **Add one or more actions**

Add built-in logic, catalog actions, connector actions, wallet actions, or onchain actions. B3OS validates each node against its action schema.
  **Reference prior data with expressions**

Use expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetchPrice.result.price}}`, `{{$props.asset}}`, and loop variables like `{{$item}}`.
  **Test the draft**

Run the workflow with sample input. Inspect node status, payloads, masked secrets, timing, and failures before publishing.
  **Publish the live version**

Publish when the draft passes validation. Schedules, webhooks, and event listeners use the published live version.

**You now have a live workflow**

A published workflow has a versioned definition, an active trigger surface, and run history that can be inspected from
  the app or API.

## Minimal API Flow

Use the API when you need to automate workflow creation, run a workflow from another service, or manage B3OS from your own backend.

```bash curl
curl -X POST https://api.b3os.org/v1/workflows \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Daily price check",
    "definition": {
      "nodes": []
    }
  }'
```

```javascript node.js
const response = await fetch("https://api.b3os.org/v1/workflows", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.B3OS_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    name: "Daily price check",
    definition: { nodes: [] },
  }),
});

const workflow = await response.json();
```

```python python
import os
import requests

response = requests.post(
    "https://api.b3os.org/v1/workflows",
    headers={
        "Authorization": f"Bearer {os.environ['B3OS_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "name": "Daily price check",
        "definition": {"nodes": []},
    },
)

workflow = response.json()
```

## First Workflow Patterns

**First workflow shape**

**Trigger**
  **Context**
  **Action node**
  **Policy branch**
  **Notify or transact**
  **input**
  **expressions**
  **run**
  **result**
  **approved path**

**[Webhook to Slack](/platform/webhooks-executions)**

Receive an external event, transform it, and notify a Slack channel.
  **[Schedule to DeFi read](/actions/defi)**

Check markets or positions on an interval and route the result through logic nodes.
  **[EVM event to transaction](/actions/evm-onchain)**

Listen for an onchain event, evaluate policy, and execute through an organization wallet.

## What to Read Next

**[API Quickstart](/examples/api-quickstart)**

Create, validate, publish, run, and inspect a workflow from copy-paste API requests.
  **[Recipes](/recipes)**

Start from common workflow patterns such as webhook alerts, scheduled checks, approvals, and x402 calls.
  **[Concepts](/platform/concepts)**

Learn the vocabulary: workflows, nodes, runs, executions, triggers, connectors, wallets, props, and CU.
  **[Authentication](/api/authentication)**

Create API keys, understand scopes, and decide when to use user sessions versus service credentials.