Workflow Editor
The Workflow Editor is GLIK’s visual logic builder for designing intelligent, reusable workflows across departments, systems, and tools — enabling enterprises to rapidly automate complex operations.
The Workflow Editor is GLIK's visual interface for designing app logic using modular blocks. Whether you're building a simple approval flow or a complex orchestration of memory, decision branches, and tool integrations, the Workflow Editor is where you structure, connect, and configure the logic behind every GLIK application.
This page explains how the Workflow Editor fits into the broader GLIK Cloud ecosystem, how it relates to core app types and execution models, and how it operates consistently across both GLIK Cloud and GLIK Open Core environments.
Not all Chatbot and Agent apps open the Workflow Editor
Some apps — especially those using the Chatbot or Agent App Types — may launch into a Prompt Orchestration Interface instead of the visual Workflow Editor. This prompt-based view supports single-step agents that operate from a single instruction box, using variables, tools, and memory, but without canvas-based block chaining.
If your use case requires conditional branching, memory-scoped flows, or agentic orchestration, use:
Advanced Chat App Type for memory-aware conversations
Workflow App Type for full logic orchestration
The visual Workflow Editor is always available — but must be accessed via App Types that support multi-step logic or by switching to canvas mode where supported.
What is the Workflow Editor?
The Workflow Editor is a canvas-based design interface that allows users to build logic visually. You arrange blocks such as Variable Assigners, Tool Nodes, LLM Blocks, Conditional Branches, and more — connecting them in sequence or through branching logic to form a complete workflow.
Every GLIK App — regardless of App Type (e.g. Chatbot, Agent, Advanced Chat, or Workflow) — uses the same Workflow Editor under the hood. The App Type determines how the workflow is triggered and wrapped, but the editor itself remains consistent.
Where the Editor Fits in GLIK Cloud
The Workflow Editor connects to other core elements of GLIK Cloud:
What Is a Workflow? Introduces the conceptual definition of a workflow — a sequence of logic blocks. → The Editor is where you build and deploy that logic.
App Types (Overview) Describes the differences between Chatbot, Agent, Advanced Chat, and Workflow app types. → All App Types are powered by logic designed in the Editor.
Workspaces & Permissions Determines who can edit workflows, view logs, or deploy apps. → The Editor is scoped by workspace and role permissions.
Security & Data Handling Defines how execution data and variable values are handled across blocks. → The Editor enables block-level memory control and secure data routing.
Also Available in GLIK Open Core
The GLIK Open Core version of the platform includes the same Workflow Editor interface. Whether running in GLIK Cloud or self-hosted Open Core, developers and enterprise users interact with the same visual logic designer — ensuring consistent experiences across deployment models.
This consistency allows partners and internal teams to:
Prototype in Cloud, deploy on-prem
Reuse workflows between hosted and self-managed environments
Train contributors on one system and port across environments
Use Cases for the Workflow Editor
Policy Enforcement Logic
Expense approval workflows with scoped memory thresholds
Contextual Automation
Email triage, CRM updates, or HR onboarding flows
Embedded Agents
Templates used in Advanced Chat or Agent App Types
API & Tool Integration
Executing tool nodes (e.g., external API calls)
Orchestration of Subflows
Triggering nested logic paths across large organizations
Editor Behavior
Drag-and-drop UI with real-time logic validation
Input mapping and output variable assignment per block
Error handling logic and retry configuration
Integration with Save Point Agent, variable scopes, and memory blocks
Preview mode and execution logs (if permissions allow)
Last updated
Was this helpful?