Build manually
Manual build is the classic path: you open the visual builder, place nodes on the canvas, draw routes between them, and fill in every field. Nothing is generated for you; you decide the trigger, the logic, and how data moves from step to step.
This is how most people learn Latenode. It also stays the best option when you need exact control over conditions, branching, or custom JavaScript.
When to choose manual build
- You are new and want to understand how scenarios work.
- The flow has strict rules (amounts, branches, custom code).
- You are fine-tuning a scenario someone else started (AI, template, or MCP).
- You need to inspect every node setting before going live.
What you work with
Every scenario starts with a trigger: schedule, webhook, app event, or Run once for testing.
After the trigger come action nodes: app integrations, JavaScript, iterators, and core nodes. Routes (connectors) pass data from one node to the next. Use route conditions when the scenario should split into branches.
For terminology, see How Latenode works.
Build step by step
Create a scenario
From Scenarios, click Create scenario. You land on an empty canvas in the Development branch.
Add a trigger
Click Add node and pick a trigger: Trigger on Schedule, Trigger on Webhook, an app trigger, or Trigger on Run once while you are still testing.
Add and connect actions
Click the connector on the right of a node to add the next one already wired up, or use Add node and draw routes manually. Fill in required fields in each node.
Pass data between nodes
Open the DATA tab on a node to pick fields from previous steps. See How to build a scenario for connectors, routes, and variable syntax.
Test in Development
Click Run Once. For webhooks and app triggers, send a real event if the node needs one. Open Execution History to inspect output per node.
Deploy and activate
When Development looks good, click Save, then Deploy to copy the version to Production. Turn Active on so triggers run the live branch.
Tips while you build
- Save often: unsaved changes are easy to lose on a busy canvas.
- Start linear: one trigger and a short chain before you add branches.
- Connect authorizations once and reuse them across nodes.
- Use Use Execution Data from a past run when you need real input without re-running the whole scenario.
Go deeper
- Your first scenario in 15 minutes - guided tutorial
- How to build a scenario - canvas mechanics
- Building scenarios - save, run, deploy
- Routes - conditions and branching
Introduction
Latenode is an AI workflow automation platform. Connect 5,500+ integrations, use 1,200+ AI models without API key management, and automate anything from simple tasks to multi-agent systems.
AI scenario helper
Describe the task in chat; the assistant proposes a plan and builds the scenario on the canvas.
Need Help? Ask the community
If something on this page is missing or unclear, post on the Latenode community forum. Our team and other users usually reply quickly.