Sequential Node Setup in Agent Studio: A Step-by-Step Guide

The Sequential Node runs multiple actions in a fixed order inside one node. Use it when the flow is predictable and needs to be controlled — collecting user info, calling APIs, or chaining a series of actions.

What the Sequential Node does

Agent Studio builds agents from triggers and nodes. A Sequential Node fires when it receives input from a trigger or another node, then executes its configured steps top to bottom. Instead of adapting to context like an AI Agent Node, it follows a structured path.

Each step inside a Sequential Node is a processing node — the individual action that runs in sequence.

Before using it: make sure a trigger is configured to start the agent.

Why use a Sequential Node

• Executes steps in a clear, predefined order.
• Predictable, repeatable outcomes.
• Groups multiple steps into a single node.
• Cleaner data collection.
• Less node sprawl than chaining separate nodes.

Core elements

Processing nodes

Each step is a processing node that defines an action: capture input, call an API, generate content.

Step execution order

Nodes run top to bottom. Each step must finish before the next begins.

Processing node types

Three categories cover most use cases:

• Capture Information — collect email, phone, text, or single-choice input.
• Actions and API — perform internal operations or hit external systems.
• AI Generation — generate text, images, video, or audio.

Processing node types in detail

Email Address

Validates email format before continuing. Captured email is stored as a runtime variable.

Phone Number

Captures and validates a phone number, typically requiring a country code. Stored as a runtime variable.

Text Input

Free-form input with optional minimum and maximum length. Stored as a runtime variable.

Single Choice

Presents predefined options as buttons. The selected option is stored as a runtime variable for routing.

API Call

Sends a request to an external system. Configure endpoint, headers, and body. Use variables to make the request dynamic. The response is stored as a runtime variable.

Actions

Performs predefined system operations — updates, triggers, etc. — to convert collected data into real changes.

Text, Image, Video, and Audio Generation

AI generation nodes that produce dynamic content from a prompt. Audio generation uses text-to-speech. Use variables to personalize the output.

Variables: data flow between steps

Every processing node creates a runtime variable from its output. Reuse those values in later steps via the variable picker ({}).

Example: a user enters rahul@email.com in an Email step. The next text step references {{email}} and sends "Thanks! We'll contact you at rahul@email.com shortly."

How to configure a Sequential Node

1. Add the Sequential Node from the Nodes panel and connect it to a trigger or previous node.
2. Add processing nodes. Click Add a processing node to start building.
3. Configure each step — prompts, validation, behavior.
4. Order the steps. Execution depends on order.
5. Use variables between steps. Click the {} picker to insert a previous step's output.
6. Add Actions or API Calls. Use earlier-step variables in headers, body, or action fields.
7. Connect to the next node in the agent flow.

FAQ

When should I use Sequential Node instead of AI Agent Node?

Sequential Node for structured, predictable flows. AI Agent Node when you need dynamic decision-making or open conversation.

Why doesn't my API call adapt like an AI response?

API calls in Sequential Nodes run directly without AI interpretation. For reasoning, route the response through an AI Agent Node.