> ## Documentation Index > Fetch the complete documentation index at: https://docs.hitl.sh/llms.txt > Use this file to discover all available pages before exploring further. # Workflow editor > A tour of the editor at my.hitl.sh: the canvas, adding steps, the trigger, review steps, and the Executions, Humans and Settings tabs. You build workflows in the editor at [my.hitl.sh](https://my.hitl.sh). Open **Workflows** to see yours (and, under **Shared with you**, the ones you review). ![The Workflows page listing six workflows with their reviewers, trigger, last activity, status Active or Draft and number of runs](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/app/workflows.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=600890f4b4d74f480b671efce423629e) ## Start a workflow Click **New workflow**. Describe it in a sentence and HITL drafts the steps, start from an example (refunds, email replies, social posts, change requests, ...), or click **I'll design it myself** for an empty canvas with a Start and an End. ![What workflow would you like to build today: a text box to describe it, I'll design it myself, and example workflows to start from](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/app/new-workflow.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=658bd3a2cd42fd6272bbdefcafff7a18) **Import** on the Workflows page loads a workflow from a JSON file. ## The canvas The top bar has four tabs, **Canvas**, **Executions**, **Humans** and **Settings**, and on the right **Test**, **Activate** (or **Pause** when live) and save. * Click a step to open its settings on the right. * Drag from a step's handle to another step to connect them. A condition has a **True** and a **False** handle. * The toolbar at the bottom: select, pan, **Auto align**, and **+** to add a step. Zoom with the controls on the left or ⌘+ / ⌘−. * The box next to the toolbar is the workflow assistant: select steps and ask it to change them. ![The Add node menu open over the canvas, listing Human Review, AI, AI Classifier, Data, Condition, Transform and Action](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/editor/add-step.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=941265422380d5dbc46dfa99f14efd12) What each step does: [Workflows → Steps](https://docs.hitl.sh/concepts/workflows.md#steps). ## The trigger Click **Start** to choose how runs begin: **Webhook**, **Email**, **Schedule**, **Manual** or **Google Sheets**. A webhook trigger shows its URL and a **Test payload**: sample JSON used by **Test** and by the review step's phone preview. Fields you add there become insertable chips in later steps. ![The Start step's settings: trigger types Webhook, Email, Schedule, Manual and Google Sheets, the webhook URL, and a test payload with order\_id, customer name and email](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/editor/trigger.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=9760a5603f9b1629d0fe2d5737f19e3c) Every workflow can also be run with the API, CLI, MCP, n8n, Zapier and Make, whatever its trigger. ## Review steps Select a review step, then **Edit request** to write the question and pick the answer type, and **Reviewers** to say who answers and where. The phone preview shows exactly what reviewers will see. ![The Edit request dialog of the Approve refund step with its question, answer options and a phone preview](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/editor/edit-request.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=48b1d9e299029aff7005a7901b91afe4) ![The Reviewers tab: who answers, routing and the channels the request is sent to](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/editor/reviewers.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=e6b921146ad03cfbb1c70c00226b8087) Every setting is explained in [Review steps](https://docs.hitl.sh/concepts/review-steps.md). ## Test and activate * **Test** runs the workflow with the trigger's test payload. Review steps ask people as usual; action steps only log what they would send. * **Activate** checks the workflow and makes it live. If something is missing, such as a review step without a question, it says what to fix. **Pause** stops new runs. ## Executions Every run, newest first, with its status (**Waiting for review**, **Completed**, **Failed**, ...). Expand one to see its input, each decision and what each action sent and got back. ![The Executions tab of the Refund approval workflow listing two runs waiting for review and two completed runs](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/editor/executions.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=703961146b22b600a6f6187f88faf6fc) ## Humans The workflow's reviewers, its join code, link and QR code, and an invite-by-email form. See [Reviewers](https://docs.hitl.sh/concepts/reviewers.md). ## Settings The icon and colour (shown in lists and on reviewers' phones), name, description, status, trigger type, webhook URL, and **Delete this workflow**. ![The Settings tab with the workflow's icon, name and description, its status Active, trigger type Webhook, creation date and webhook URL](https://mintcdn.com/hitl/8U4JOCXRGxwTV383/images/editor/settings-tab.png?fit=max\&auto=format\&n=8U4JOCXRGxwTV383\&q=85\&s=7dfff04fd03e6c6dbb1c73cfce4cd09c) ## Building with an agent **Connect Claude** in the editor's top bar prints a command (`npx hitl-workflow ''`) that lets Claude Code read and edit the workflow you have open, live: you see its changes on the canvas as it makes them. An agent can also build workflows through the API or MCP (`create_workflow`, `invite_to_workflow`, `activate_workflow`). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.