🧩Overview

🧩 A workflow is the logic that turns a customer message or event into an action through connected steps.

A workflow in Wkil is a sequence of defined steps that you create once and run repeatedly with new inputs, such as every new customer message.

Parts of a workflow

• Trigger: Where the workflow starts and what it passes in (WhatsApp message, API request, schedule, or event from a connected system). Each workflow has one trigger.
• Action/Block: One step that does one job: an Agent reasons with a model, a Function runs logic, a Condition branches, or a Loop repeats work.
• Connection: Links one step to the next and determines execution order.
• Output: What a step produces for later steps to read.

🔧 An action is not a tool. A tool is a capability the agent may call during a step, such as sending a WhatsApp message, searching a knowledge base, or reading a CRM. The agent decides which tools to call and when.

Block types

• Work blocks: Agent, Function, and API Request.
• Routing blocks: Condition, Router, Loop, and Parallel.
• Run-shaping blocks: Response, Guardrails, and Wait. Two larger families are Apps, which connect external services, and Triggers, which start workflows.

How a workflow starts and runs

The trigger determines when a run begins and what input it receives. Steps then execute according to their dependencies: each step starts as soon as the steps it depends on finish, so independent paths can run in parallel.