How It Works
Every flow starts with an entry node (such as a Start Node, Webhook, or Cron) and connects through action nodes. Flow Activation runs this entire pipeline with test data so you can see exactly what happens at each step.
Running a Flow
Click the play button
Click the play button on the Start Node of your flow. This opens the Test Flow dialog where you can configure the input data for your test run.
Configure test data
Choose between Use Test Data (auto-generated mock data based on your node configuration) or Custom JSON Input to provide your own payload. VibeFlow analyzes downstream nodes and generates realistic mock values — for example, a 
text field gets "Mock text" as a default value.Observe execution
Once you click Run Test, VibeFlow executes each node in topological order. Nodes light up as they execute — transitioning from idle to executing to completed (or error). Edges animate to show data flowing between nodes.
Captured Input & Output
Every node in an activated flow captures the data it received and the data it produced. This makes it straightforward to trace how data transforms as it moves through your workflow.Captured Input
The input panel shows the exact payload a node received from its upstream connection. In this example, the Create Todo mutation node receives thetext field from the Start Node input.
Captured Output
The output panel shows what a node returned after execution. For a mutation insert, this includes the newly created document with its generated_id and id fields alongside the input data.
Auto-Generated Test Data
When you select Use Test Data, VibeFlow automatically generates mock values based on your node configuration:| Field Pattern | Generated Value |
|---|---|
email | test@example.com |
name | John Doe |
text, description | Mock text |
| Number fields | 42 |
| Boolean fields | true |
| Date fields | Current ISO timestamp |
| ID fields | mock_<field>_<random> |
Authentication Toggle
Nodes that support authentication display an Auth toggle at the bottom. When enabled, the node requires a valid user session to execute. During flow activation, authentication is automatically simulated — VibeFlow stubs auth calls with a simulated user identity, so auth-enabled nodes execute normally without requiring a real login session.Error Handling
If a node fails during activation, it shows an error state with the error message. Downstream nodes are automatically skipped when an upstream node fails, so you can quickly identify the root cause of issues without wading through cascading errors.Flow Activation uses a sandboxed environment for execution. Database mutations during testing use
convex-test and do not affect your production data.