Prompt Orchestration Interface

A fast, instruction-first interface for building lightweight AI agents using prompts, tools, and context — without requiring visual workflow design. Ideal for rapid prototyping.

The Prompt Orchestration Interface is GLIK’s streamlined environment for designing lightweight, single-instruction agents. It allows users to rapidly build apps like chatbots, form assistants, or tool-driven prompt chains by entering structured instructions, attaching tools, and referencing memory or documents — all without needing to compose logic block by block.

This is the default interface presented when creating Chatbot or Agent apps in GLIK Studio, making it the starting point for most beginner and intermediate use cases.

What “Workflow” Means

The word “workflow” is used in three different contexts within GLIK:

  1. Workflow (App Type) — A specific GLIK execution model designed for automating logic using a block-based interface. It’s one of the four foundational app types alongside Chatbot, Agent, and Advanced Chat.

  2. Workflow (Architecture) — A broader concept referring to the high-level orchestration of tasks, inputs, tools, and decisions across GLIK apps. This includes how agents interact, how memory is passed, and how execution flows are triggered across systems.

  3. Workflow (Editor View) — The visual interface where you arrange blocks and nodes (like Variable Assigners, Tool Nodes, LLM Blocks, etc.) to construct executable logic paths. This is where low-code users build and configure the logic of any GLIK app, even outside the Workflow App Type.

In short: the Workflow App Type is one way to execute workflows — but “workflow” as a term also describes how logic flows and systems connect across all App Types.

What is the Prompt Orchestration Interface?

This interface is a form-based, instruction-first builder for orchestrating AI behavior in GLIK. Instead of constructing a canvas of connected blocks, users enter:

  • A main instruction prompt

  • Optional variables, such as {{user_question}} or {{invoice_total}}

  • Attached tools (e.g. Vision, Document parsing, Web Search)

  • Context from Knowledge or uploaded content

📣 Try GLIK

Explore and deploy your first app at app.glik.ai

Apps built in this interface execute as a single-pass instruction pipeline. This is ideal for:

  • Quick support bots

  • Verification tools (e.g. invoice checkers, policy retrievers)

  • Document readers or summarizers

  • Internal tool wrappers with minimal branching


How It Compares to the Workflow Editor

Feature
Prompt Orchestration Interface
Workflow Editor

❌ No

✅ Yes

❌ Limited

✅ Full branching with nodes

Memory Routing

🔸 Basic variable use

✅ Scoped memory, save points

Tool Integration

✅ Supported (predefined tools)

✅ Supported (with block logic)

Multi-step Flow

❌ Single prompt only

✅ Multi-block orchestration

Ideal For

Fast setups, atomic tools

Complex logic, conditional workflows

This screen shows the form-based interface used to configure a single-instruction GLIK Agent. The INSTRUCTIONS field contains the core prompt logic, while variables, tools, and knowledge can be added to enhance functionality. The live preview pane on the right displays example responses based on the configured logic, enabling fast iteration and testing without needing the full Workflow Editor.

The Prompt Orchestration Interface is optimized for speed and simplicity. The Workflow Editor is optimized for custom orchestration and reusable logic structures.

App Type
Default Editing Mode
Notes

Chatbot

Prompt Orchestration Interface

Stateless logic

Agent

Prompt Orchestration Interface

Stateful, tool-using

Advanced Chat

Workflow Editor

Multi-turn, memory-driven

Workflow

Workflow Editor

Logic-first orchestration

Apps created in Chatbot or Agent modes begin in the Prompt Orchestration Interface, but logic can be migrated to the Workflow Editor for more advanced customization when needed.


Key Capabilities

  • Instruction chaining with variables

  • Tool & plugin integration (e.g. OCR, Web Search, Vision)

  • Knowledge referencing (connect document or markdown)

  • Fast preview and deployment

  • Single prompt memory and input binding


When to Use Prompt Orchestration

Use the Prompt Orchestration Interface when:

  • You need to build fast, utility-style AI agents

  • The logic fits into a single instruction or task

  • You are wrapping existing tools or documents

  • You’re building early-stage prototypes before scaling into orchestration


Upgrade Path

As workflows evolve or grow in complexity, users can transition from the Prompt Orchestration Interface into the Workflow Editor, unlocking conditional branches, scoped memory, save points, and full orchestration logic.

GLIK gives teams the flexibility to start fast and scale into complexity — without rewriting their apps.

Last updated

Was this helpful?