# Manual Run

### Overview

The **Manual Run** trigger allows you to execute a workflow **on demand** with a single click. It is designed for testing, debugging, and ad-hoc executions where you want full control over when a workflow runs.

Unlike time-based or automated triggers, Manual Run only executes when explicitly initiated by the user.

***

### What Manual Run Does

Manual Run acts as a **user-initiated trigger** that starts the workflow instantly when clicked. It does not rely on schedules, events, or external conditions.

Key capabilities include:

* Instant workflow execution
* Safe testing of nodes and integrations
* On-demand execution without automation
* Ideal for development and debugging workflows

***

### How It Works

* The **Manual Run** node appears on the canvas as a trigger.
* Clicking the **Run** (play) button immediately starts the workflow.
* All connected nodes execute sequentially based on the workflow logic.
* No background or recurring execution occurs.

***

### Configuration Options

The Manual Run trigger requires **no configuration**.

There are:

* No time settings
* No repeat intervals
* No parameters

This simplicity ensures predictable, controlled executions, on-demand - directly from the canvas.

***

### Common Use Cases

* **Testing workflows before deployment**
* **Debugging smart contract interactions**
* **Triggering one-off blockchain transactions**
* **Running ad-hoc data reads or API calls**
* **Validating integrations and node outputs**

***

### Example Workflow

**Scenario:** Test a fund transfer workflow before scheduling it.

1. Use **Manual Run** as the trigger.
2. Connect wallet, set variables, and add a fund transfer node.
3. Click **Run** to execute instantly.
4. Review logs and results.


---

# 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://wiki.decimal.at/technical/node-directory/manual-run.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.