# What Is a Workflow?

A **workflow** in GLIK is a modular, visualized execution graph that automates how tasks, tools, memory, and AI reasoning blocks are connected to complete a business objective.

Think of it as the **operating logic** behind any intelligent automation: from handling an invoice approval to triaging support tickets, surfacing knowledge from memory, or making policy decisions — the workflow is what determines what happens, in what order, and under what conditions.

<details>

<summary>Summary</summary>

In GLIK, a workflow is the bridge between business intent and system execution. It turns policy, memory, logic, and reasoning into a transparent and governable automation path — designed for enterprise-grade AI deployment.

It is the foundational structure for [intelligent agents](/introduction/what-is-an-agent-application.md), modular automation, and strategic reuse across the organization.

</details>

## Strategic Enterprise Value

GLIK workflows are designed not just for automation — but for **governed, explainable, and composable orchestration** at enterprise scale.

| **Value**                        | **Description**                                                                                                                              |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| ✅ **Business Continuity**        | Eliminates manual bottlenecks by formalizing business logic into repeatable structures — reducing operational overhead and human dependency. |
| 🔒 **Auditability & Governance** | Ensures workflows are visible, versioned, and fully traceable, enabling audit readiness and policy compliance across departments.            |
| 💰 **Cost Optimization**         | Automates routine or rules-driven decisions (e.g., approvals, routing, extraction), minimizing human workload and escalation risks.          |
| 🧱 **Enterprise Modularity**     | Each workflow block is a modular, interchangeable unit — enabling scalable orchestration patterns and cross-team reusability.                |

## How Workflows Work&#x20;

* Built visually in [**GLIK Studio**](/glik-cloud/getting-started/glik-cloud-vs.-glik-studio.md) using a drag-and-drop canvas
* Deployed and executed in **GLIK Cloud**, where memory, orchestration, and runtime conditions are managed
* Comprised of blocks like:
  * **Start/End Blocks** (entry + termination points)
  * [**LLM Blocks**](/system-architecture/blocks-and-nodes/input-and-extraction/llm-block.md) (reasoning)
  * [**Tool Nodes**](/system-architecture/blocks-and-nodes/input-and-extraction/tool-node.md) (external system actions)
  * [**Conditional Branches**](/system-architecture/blocks-and-nodes/logic-blocks.md) (logic flow)
  * [**Data & Memory Blocks**](/system-architecture/glik-knowledge.md) (variable assignment, enrichment, recall)

{% hint style="info" %}

* In [**GLIK Studio**](/glik-cloud/getting-started/glik-cloud-vs.-glik-studio.md), you configure and connect the [**LLM Block**](/system-architecture/blocks-and-nodes/input-and-extraction/llm-block.md) as a visual component. This is part of the front-end orchestration interface — it’s a block.
* When the app is **saved, deployed, or executed** in GLIK Cloud, that block is [**compiled into a node**](/system-architecture/blocks-and-nodes.md) that becomes part of the backend execution graph. This is what actually processes data, handles memory injection, and returns results.
  {% endhint %}

## For Enterprise Leaders & Decision Makers

Workflows are not just technical tools — they are:

* **Policy enforcement engines** (e.g., GLIK can encode thresholds, rules, escalation logic)
* **AI transformation blueprints** (showing exactly how and where AI decisions are made)
* **Reusable operational IP** (codifying best practices across departments)

They allow non-developers to visualize and reason about how intelligent systems are structured — without writing code.

***

### For Developers & Builders

While developers can dig into DSL and config layers, workflows in GLIK serve as the top-level executable unit.

* Every app ([Agent](/app-types/agent.md), [Workflow](/app-types/workflow.md), [Chatbot](/app-types/chatbot.md), etc.) is backed by a workflow
* Developers can inspect and debug each node in a flow
* Workflows can evolve over time as business logic changes — no rebuild required


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glik.ai/glik-cloud/what-is-a-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.