Scenarios

In Latenode, an automation is called a Scenario. A Scenario is a chain of Nodes connected on a visual canvas. Each Node performs one step and passes its result to the next Node.

Trigger → Action → Action → Result

The exact steps depend on the service and process you are automating.

Scenario types

Latenode documentation describes five common types of Scenario:

Linear scenarios

The same Nodes run in the same order every time.

New form submission → Save to a spreadsheet → Notify the team

Conditional scenarios

The Scenario chooses a route based on structured information such as status, amount, country, or score.

New request → Check amount → Notify manager or send an automatic reply

AI-based routing

The Scenario uses AI when the decision depends on meaning, tone, intent, or other unstructured information.

Incoming message → AI classifies the message → Route to the right action

Agent scenarios

An AI Agent chooses which connected tools to use and in what order. This is useful for flexible requests that cannot be described as one fixed sequence.

Multi-agent scenarios

Several specialised agents work together on a larger task. This is intended for complex work that naturally separates into roles such as research, writing, review, or publishing.

Build a Scenario

Describe the result you want.
Decide what starts the Scenario: an event, a schedule, a webhook, or a manual run.
Choose the Nodes needed for each step.
Connect the Nodes from left to right.
Run the first Node once and inspect its output.
Map the required information into the next Node.
Test each step in order.
Save and activate the Scenario when the result is understood.

Routes and conditions

A Node can have more than one outgoing route. A route can have a condition so that it only runs when the condition is met. A fallback route can handle cases where none of the other conditions match.

New lead
├── Budget is high → Notify sales manager
└── Otherwise      → Send information email

Development and production

Test a Scenario before activating it for real events. Depending on the trigger, Latenode may provide separate development and production behaviour. Confirm which branch, URL, schedule, or external event is being used before activation.

Scenario types and complexity

Start with the simplest type that fits the process:

| Need | Suitable type | |---|---| | Always the same sequence | Linear | | Clear field-based decisions | Conditional | | Decisions based on meaning or tone | AI-based routing | | AI chooses the tools and order | Agent | | Several specialised AI roles | Multi-agent |