# Workflow

The **Workflow App Type** is GLIK’s most structured execution model, designed for automating rule-based processes using a visual block-based interface. It excels in scenarios where inputs, logic branches, and system behavior can be clearly defined up front. This makes it ideal for implementing **repeatable, auditable, and governed enterprise operations** — especially where compliance, routing, or integration requirements are complex but predictable.

{% hint style="info" %}

## What “Workflow” Means 

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

1. [**Workflow (App Type)**](https://docs.glik.ai/app-types/workflow) — 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](https://docs.glik.ai/app-types/chatbot), [Agent](https://docs.glik.ai/app-types/agent), and [Advanced Chat](https://docs.glik.ai/app-types/advanced-chat).
2. [**Workflow (Architecture)**](https://docs.glik.ai/system-architecture/execution-model/workflow-architecture) — A broader concept referring to the high-level orchestration of tasks, inputs, tools, and decisions across [GLIK apps](https://docs.glik.ai/app-types). This includes how agents interact, how memory is passed, and how execution flows are triggered across systems.
3. [**Workflow (Editor View)**](https://docs.glik.ai/glik-cloud/workflow-editor) — 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.
> {% endhint %}

## What sets Workflow apart?

While **Chatbots** and **Advanced Chat** are interaction-first models optimized for human-facing interfaces, **Workflow is system-first**. It doesn't rely on conversation — instead, it executes decisions, data transformations, or system calls based on preconfigured logic flows. Think of it as a **logic circuit for enterprise tasks**, where each block is a switch, each variable a wire, and each output a controlled signal.

Enterprises use GLIK Workflows to:

* Automate **multi-step approvals**
* Execute **decision trees based on policy thresholds**
* Trigger **system integrations or API calls**
* Coordinate **cross-system actions** like ticket generation or database updates

This App Type is often embedded as the **core logic engine** beneath other experiences — such as agents or conversational frontends — making it the backbone of scalable orchestration in enterprise environments.

{% embed url="<https://www.mermaidchart.com/raw/21d6fd94-1efd-49f0-b878-c22056fbd1da?theme=light&version=v0.1&format=svg>" %}
How users move from conceptual understanding to practical application of the Workflow App Type. It helps teams recognize when system-driven logic is more efficient than conversational AI, leading to faster deployment of rule-based automations.
{% endembed %}

## Why not just use Advanced Chat?

Advanced Chat is ideal when workflows must adapt to user responses, unknown inputs, or free-form conversations — but when the flow of logic is **predictable**, predefined, and not reliant on long-form input, **Workflow is more efficient and easier to maintain**. It provides:

* **Full visibility** over logic and branching
* **Clear audit trails** for compliance and governance
* **Reusable logic blocks** across multiple apps or templates

In short: **Use Advanced Chat when user input drives logic**; **use Workflow when logic drives execution**.

***

## When to choose Workflow

| App Type          | Best When…                                  | Input Type             | UI Model                 |
| ----------------- | ------------------------------------------- | ---------------------- | ------------------------ |
| **Chatbot**       | You need static responses to simple prompts | Stateless messages     | Simple Q\&A              |
| **Advanced Chat** | Conversations shape logic, memory required  | Multi-turn dialogue    | Dynamic chat             |
| **Workflow**      | Execution follows clear, visual logic paths | Form, variable, system | No chat; system-executed |

## Enterprise Value&#x20;

GLIK’s Workflow App Type is the fastest way for enterprises to **digitize and automate legacy processes** without requiring new software or retraining end users. Whether triggered by a form submission, agent escalation, or system event, workflows handle the invisible heavy lifting — evaluating inputs, applying rules, and orchestrating downstream actions.

> GLIK Workflows turn static rules into real-time automation, enabling legacy systems to operate with AI-like responsiveness — without modification.