# Introduction

Ondeva’s **Workflow engine** is where your application logic comes to life. It’s built for **precision automation, powerful integrations**, and **cross-system control**—without writing backend code.

Whether you're building a startup MVP, internal tool, client portal, or enterprise process—Workflows allow you to define the **logic, triggers, and data flow** that make your application smart, dynamic, and autonomous.

Unlike traditional no-code automators, Ondeva workflows combine **developer-grade logic** (API calls, loops, branching, async execution) with a visual builder that’s designed for clarity, speed, and reuse.

***

### **What You Can Do with Workflows**

* Automate actions triggered by **forms, button clicks, page loads, or time schedules**
* **Read, write, transform, and delete data** in your unified data layer
* **Call external APIs**, pass and parse responses
* Build modular logic using conditions, loops, and sub-workflows
* Run **AI-powered steps** like text generation, keyword extraction, and audio transcription
* Handle user identity, enforce licensing, and manage session-based logic
* **Trigger client-side actions** like navigation, downloads, and analytics events

***

### **How It Works**

* You build logic visually on a drag-and-drop **canvas**
* Each workflow consists of **steps** (actions) and **events** (triggers)
* You can pass data via **variables and session parameters**
* Every workflow is fully debuggable and testable before going live
* Once published, it’s available app-wide — and reusable across forms, buttons, APIs, and more


---

# 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.ondeva.com/workflow/introduction.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.
