# Glossary

***

#### **Workflow**

A programmatic sequence of steps triggered by an event and executed automatically by Wundaflow. Workflows can be paused, resumed, cancelled, and queried via API.

***

#### **Task**

An individual operation within a workflow. Tasks can be native JavaScript functions, external API calls, or serverless function invocations.

***

#### **Trigger**

A condition or event that starts a workflow execution. Triggers can be based on blockchain events, schedules, API calls, or other third-party system events.

***

#### **Signal**

A message sent into a running workflow to update its state or resume execution from a paused state.

***

#### **Worker**

An external component that polls for and executes tasks defined in a workflow. Can be used to integrate custom logic or handle domain-specific operations.

***

#### **Webhook**

A real-time HTTP POST message sent to your application to inform it of events in a workflow lifecycle or other system-level events.

***

#### **Retry Policy**

A configuration attached to tasks or workflows that defines how failed steps should be retried, including back-off strategy and limits.

***

#### **KV Store**

A key-value store either (1) scoped to a single workflow execution, used to persist lightweight data between tasks; or (2) scoped to global context, used to persist long-term data across all workflows.

***

#### **Wallet**

A blockchain wallet that can be generated, managed, and used to sign transactions as part of a workflow. Wundaflow can generate wallet addresses programmatically.

***

#### **Connector**

A prebuilt integration with a third-party platform (such as AWS, OpenAI or Replicate). Enables Wundaflow to execute functions using customer-provided credentials without needing to host infrastructure.

***

#### **Execution**

A specific instance of a workflow being run with defined inputs. Executions have a lifecycle and can be monitored or controlled via API.

***


---

# 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.wundaflow.com/glossary.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.
