Workflow Guide

01 — Why

Why you need workflows

Every job has repetition. Checking inventory each week, finding low-stock products, comparing suppliers, creating purchase orders, getting approvals, and reporting results. It takes one hour each time, but done weekly, that adds up to 52 hours a year.

Traditional automation tools tried to solve this problem, but they required development skills or complex configurations. Even with drag-and-drop block connectors, you still had to manually set up API authentication, data transformations, conditional branches, and loop handling.

wiiiv workflows are different. Describe what you want to do through conversation, and AI designs an executable workflow. From login to purchase order approval and email delivery, AI assembles every step, and all you need to do is confirm.

wiiiv workflows are the first workflow system that converts conversation into executable automation. No code to write, no blocks to drag. Just describe the outcome you want.

02 — Difference

How it differs from existing workflow tools

Limitations of existing tools

Tools like Zapier, Make, and n8n use a "trigger + action" model. Users manually select each step, map fields, and configure authentication. Once conditional branches or loop handling are added, complexity increases dramatically.

The wiiiv approach

Conversational input: Just say "Look up SkyMall best sellers and low-stock items, check supplier performance, place orders, and send an email report"
AI design: The entire flow is assembled automatically: authentication, API calls, data joins, loops (supplier lookup / performance check / order creation / approval), report generation, and email delivery
Governed execution: Every step leaves an execution record and verification trail, providing transparent tracking of what was executed and how
Reuse: Once created, a workflow can be re-run with a single button, shared with teammates, or called externally via API

03 — Node Map

How to read a node map

When you create a workflow, a node map is generated. Each node represents a single task step, and they execute sequentially from top to bottom. Below is the node map for an actual "Supplier Order Audit and Email Report" workflow.

WORKFLOW NODE MAP Supplier Order Audit and Email Report #f23323ef 10 nodes

Created: 2026-07-12T07:12:00Z

💡

API

📦 SkyStock 📊 Report ✉ Email

#1 📦 login-skystock ACT SkyStock

Logs into the SkyStock system and obtains an authentication token for order and supplier queries.

POST /api/auth/login

Input: credentials Output: login_result

#2 ⚙ extract-skystock-token TRANSFORM SkyStock

Extracts the accessToken value from the login response body JSON and saves it as a Bearer token for SkyStock API calls.

Parses required fields from login_result response data and saves to skystock_token list.

Input: login_result Output: skystock_token

#3 📦 fetch-all-suppliers ACT SkyStock

Retrieves the full list of suppliers from SkyStock.

GET /api/suppliers (Bearer: skystock_token)

Input: skystock_token Output: suppliers

↻ REPEAT BLOCK — suppliers

#4 ↻ repeat-suppliers REPEAT

Retrieves order history for each supplier and calculates performance metrics.

over=suppliers as=supplier | 2 inner steps

In: suppliers Out: supplier_metrics

#5 fetch-supplier-orders → #6 calculate-metrics

#5 ◆ decide-supplier-status DECIDE

Analyzes the aggregated order history per supplier to determine whether any suppliers have no transaction records.

if inactive-suppliers-exist → proceed to create_warning_report step
if all-have-order-history → proceed to create_normal_notice step

Input: supplier_order_summary inactive-suppliers-exist all-have-order-history

#6 📊 create_warning_report ACT Report

Generates a warning report based on the list of suppliers with zero orders and the overall aggregation results.

In: supplier_order_summary Out: warning_report_content

#7 🌐 create_normal_notice ACT REST API

When all suppliers have order history, generates a normal operations notice email body.

In: supplier_order_summary Out: normal_notice_content

#8 ✉ send_email DECIDE Email

Sends the generated email content based on the branch result as an actual email.

PLUGIN: mail send to="user@example.com"

In: warning_report / normal_notice Out: mail_send_result

Node map header bar

View toggle: Switch between Node Map (graph), Detail List (text), and Context (design rationale)
API tag: Indicates whether this workflow calls external APIs
Service badges: External systems integrated (SkyMall, SkyStock, Report, Email, etc.)
Hash and node count: Unique workflow identifier (#f23323ef) and total number of nodes (10 nodes)

Node card structure

Each node card displays a number (#1), service icon, node name, type badge (ACT, COMMAND, DECIDE, etc.), and service badge (SkyMall, Email, etc.). The body contains a description of what the step does, and the footer shows input/output variables.

Clicking a node flips it over to reveal technical details such as API URL, headers, body, and hints.

04 — Node Types

Node types

wiiiv workflows consist of 7 node types. Each type is distinguished by its background color and left-side color line.

⚡Act

Sends an execution request to an external system. API calls, email delivery, file saving, etc.

e.g. SkyMall product lookup, order creation, email delivery

⚙Transform

Processes data. Filtering, extraction, sorting, merging, summarization, etc.

e.g. Token extraction, low-stock filtering, report generation

👁Observe

Observes external data. Collects information without changing state.

e.g. Exchange rate lookup, server status check

◆Decide

Branches based on conditions. Splits execution into different paths.

e.g. Order validity check, severity classification

↻Repeat

Iterates over each item in a list. Contains child nodes inside.

e.g. For each product: supplier lookup, order, approval

▣SubWorkflow

Calls another workflow. Reuses a workflow you have already created.

e.g. Call a shared "SkyMall Auth" workflow

In addition to the above, there are Input (user input) and Command (Python script execution) types. Command is used when AI generates and runs Python code for joining multiple data sources or performing complex calculations.

Connections between nodes

Nodes are connected through variables. The Output of one node becomes the Input of the next. For example, the Output best_sellers from #1 fetch-skymall-best-sellers is passed as Input to #4 select-target-products.

05 — Execution

Two execution modes

wiiiv workflows can run in two modes. Choose from "Workflow Execution Mode" in the settings screen.

P Line (Python Execution)

Fast and deterministic — default

Each node is converted to a Python script and executed directly
Runs without LLM calls, so execution speed is fast
Guarantees the same result for the same input every time
Calls LLM only minimally where judgment is needed (llm.decide(), llm.generate())
Suitable for most workflows

W Line (Standard Execution)

Rich and flexible execution

The HLW engine calls the LLM for each node during execution
Provides detailed interpretation and logs for execution results
Handles unexpected situations flexibly
Suitable for tasks requiring judgment, such as report writing and analysis
Takes more execution time and cost than P Line

The default setting is P Line (Python Execution). Following the principle of "code first, minimal LLM only where needed," it runs faster and more reliably for most workflows.

06 — Create

Creating workflows from chat

The most natural way to create a workflow is to describe the task you want in a chat.

1

Describe

Describe the automation you want through conversation

2

Review

Check the node map designed by AI

3

Save

Say "run it" to save and execute at once

wiiiv — Chat

AD

하늘나무07:12 PM

Look up the top 20 best sellers from SkyMall and products with 30 or fewer units in stock. Also check CRITICAL inventory alerts from SkyStock. Filter out the ones selling well but low on stock, find their suppliers, check supplier performance, then place and approve orders. Send the full results to user@example.com. Turn this whole process into a workflow.

wiiiv07:12 PM

I analyzed the session execution history and generated a task specification.

skymall-bestseller-lowstock-procurement-and-email
v1.0 · 13 nodes

Looks up SkyMall's top 20 best sellers and products with 30 or fewer units in stock, queries SkyStock for CRITICAL inventory alerts, then filters out products that are selling well but low on stock. Checks suppliers and their performance for those products. Creates and approves purchase orders for qualifying products, then sends the full results via email.

Once AI generates the node map, you can review it right inside the chat. Say "run it" to save and execute simultaneously.

Pressing the + New Workflow button on the Workflows page also opens the chat screen with workflow creation mode activated.

Tips for writing good requests

Be specific: Instead of "look up products," say "look up products with 30 or fewer units in stock from SkyMall"
Include outcomes: Describe what to do after retrieval (report, email, order placement)
State conditions: Provide judgment criteria, such as "products selling well but low on stock"
Multiple systems: When integrating several systems, specify what each one should do ("look up from SkyMall, and also check SkyStock")

07 — Execute

Running a workflow

1. Run from the Workflows page

Select a workflow from the Workflows page, then press the ▶ Execute button in the top right. If there is an Input node, a screen for entering values appears first.

2. Run from chat

Say "run the skymall-bestseller-lowstock workflow" and it executes right inside the conversation.

3. Run via API

Check the endpoint and curl example in the API tab on the workflow detail screen.

API Endpoint

$ curl example
curl -X POST https://your-server/api/v2/workflow/a3f7dc2b/run \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{}'

4. Scheduled execution (CRON)

Set up a recurring execution schedule in the CRON tab on the workflow detail screen. You can enter a CRON expression directly, or type conversationally like "every Monday at 9 AM" and it will be converted automatically.

08 — Manage

Workflow list and management

All workflows in a project are listed on the left side of the Workflows page.

My Project

+ New Workflow

Upload

All

Mine

Shared

Auto

🔍 Search workflows...

skymall-bestseller-lowstock-...

#a3f7dc2b 13 nodes PRIVATE AUTO

Supplier Order Audit and Email Report

#f23323ef 10 nodes PRIVATE AUTO

SkyMall Order Analysis Rep...

#0caf1384 5 nodes PRIVATE

skymall-category-sales-ran...

#e299cda0 8 nodes PRIVATE AUTO

Supplier Order Audit and Email Report PRIVATE AUTO

v1.0 · 10 nodes · Retrieves the full list of suppliers from SkyStock, then aggregates order history per supplier...

WORKFLOW NODE MAP Created: 2026-07-09T17:06:05Z

SkyStock Report Email

#1 📦 login_skystock ACT

Logs into the SkyStock system and obtains an authentication token for order and supplier queries.

Output: login_result

#2 ⚙ extract_skystock_t... TRANSFORM

Extracts the accessToken value from the login response body JSON and saves it as a Bearer token for SkyStock API calls.

Input: login_result → Output: skystock_token

⋮ #3 ~ #10

Filters

All: All workflows in the project
Mine: Only workflows I created
Shared: Only workflows shared with teammates
Auto: Only workflows automatically generated by AI from chat

Right-click menu

Right-clicking an item in the workflow list reveals the following actions.

Edit in chat: Navigate to the chat screen and modify the workflow through conversation
Execute: Run immediately
Duplicate: Create a copy of the workflow
Rename: Change the workflow name
Assign color: Set a color tag for categorization (7 colors)
Toggle sharing: Switch between PRIVATE and PROJECT (team shared)
Export: Download as a .hlw.json file
Delete: Permanently delete (confirmation dialog shown)

09 — Edit

Editing a workflow

The way to modify an existing workflow is to edit it in chat. Select "Edit in chat" from the context menu, and a chat session with the workflow loaded will open.

wiiiv — Chat (Edit)

AD

하늘나무15:10

Change the delivery from email to the Slack #inventory-alerts channel. Also lower the stock threshold from 30 to 20.

wiiiv15:10

I have modified the workflow.

Changes:
• #2 fetch-skymall-low-stock: threshold 30 → 20
• #13 send-email-report → send-slack-alert: Email → Slack #inventory-alerts
• Service badge: Email → Slack

The remaining 11 nodes are unchanged. Shall I apply?

When you request changes through conversation, AI modifies only the necessary nodes and keeps the rest intact. You can also request multiple changes at once.

10 — Reuse

Reuse and extension

SubWorkflow calls

If you save a frequently used task (e.g., SkyMall authentication + token extraction) as a separate workflow, other workflows can call it via a SubWorkflow node.

Duplicate and modify

Duplicate an existing workflow, then modify only a few parts in chat to quickly create a variation.

API integration

Every workflow has a unique API endpoint. External systems or scripts can call workflows programmatically.

Sharing

Switching from PRIVATE to PROJECT allows teammates in the same project to run the workflow.

Upload / Export

You can export and upload as .hlw.json files, enabling workflow transfers between projects.

11 — Tips

Practical tips

Workflow names

AI generates names automatically, but a target-action-result pattern makes them easier to find later. e.g. skymall-bestseller-lowstock-procurement-and-email

onError policy

Each node has a failure behavior configured: retry:2 (retry twice), skip (skip), abort (stop). AI sets these automatically based on each node's nature, but you can change them in chat.

Node map zoom

Use the - 100% + controls in the top right of the node map to adjust zoom. The minimap in the bottom right provides an overview of the entire structure.

Context view

Press the 💡 (lightbulb) tab at the top of the node map to view the Genesis Context, where AI explains why it designed the workflow this way. It records the purpose, key decisions, and things to watch out for when modifying.

Community Desktop: The free version has a limit on the number of workflows. When you reach the limit, you can delete existing workflows or upgrade to Pro.

Build workflows forrepetitive tasks through conversation.