GStudio · Workflow Building

Automate repetitive multi-step work with Workflow

Orchestrate LLM calls, knowledge retrieval, code and HTTP requests with 16 node types, then publish as an API, a shared page or a workspace app. Every run is logged.

Why run repetitive work in Workflow

  • Build a multi-step process once

    The API, shared page, workspace and agents all call the same published version. Change it once and every entry point updates.

  • Trace problems, roll back mistakes

    Every run has a log tree with execution sequence, latency, tokens and credits, and earlier versions can be restored.

  • Usage you can see

    The Insights page shows total calls, success rate, credits, tokens and latency.

16 node types in 4 groups

Start and End are added by the system; add the rest to the canvas as you need them.

  • AI

    • LLM
    • Knowledge Retrieval
    • Intent Recognition

    The LLM node accepts image, document, audio and video input when the chosen model supports it, and can be given up to 10 tools, MCP tools included, which the model calls as needed. Knowledge Retrieval supports keyword, semantic or mixed search.

  • Logic

    • Conditional Statement
    • Loop
    • Batch

    Inside loops only

    • Set Intermediate Variable
    • Continue
    • Break

    Conditional branches; loops over an array or a set count, where you can also set intermediate variables, continue or break; batches of up to 10 in parallel and 200 per run.

  • Change

    • Code
    • File Parser
    • Text Processor
    • Variable Aggregator

    Process data with Python code, parse uploaded files, clean up text and merge results from several branches.

  • Tool

    • Data Table
    • HTTP Request
    • Tool

    Query data tables, send HTTP requests, or call a connected API or MCP tool directly.

Workflow at a glance

  • 16Node types to orchestrate
  • 10Parallel batch lanes
  • 200Batches per run
  • 5Async callback URLs

From debugging to production

Get it working in the draft, then publish it to the people and systems that need it.

Debug a single node and inspect its output. Before a full test run, you get a list of any run errors.

Repetitive work, built once and reused

Each scenario below uses native nodes only.

Upload a batch of contracts or reports, parse each one, pull out the key points and collect them in a single table.

Built for enterprise processes

You decide when it goes live

When changes take effect, who can use a workflow and where it runs are all up to you.

  • 01

    Draft and online versions kept apart

    Edits change only the draft and take effect when you publish. You can also cancel a publication.

    • Draft
    • Online
    • Cancel Publish
  • 02

    Review before the workspace

    Workflows are reviewed before they reach the workspace; employees can use them once approved.

    • Publish to workspace
    • Review
  • 03

    Private deployment available

    Use the public cloud, or deploy privately in your own environment.

    • Public cloud
    • Private deployment

Frequently asked questions

Workflow processes data in fixed steps without a conversation and runs via API, a shared page or the workspace. FlowAgent is for conversations that must follow set steps, and it supports handoff to a human agent.

Build Smarter AI Agents Right Now

Get 100 Free Credits Monthly!