# Manual Trigger (/docs/triggers/manual)

Run workflows on demand by clicking a button.



The simplest trigger. You click **Run** and the workflow executes immediately.

When to use [#when-to-use]

* Testing and debugging workflows during development
* One-off tasks that don't need automation
* Human-in-the-loop flows where you decide when to run

Configuration [#configuration]

The Manual Trigger node can be configured with:

| Field          | Description                                           |
| -------------- | ----------------------------------------------------- |
| Trigger Name   | Label shown on the canvas                             |
| Description    | Optional note for the trigger                         |
| Sample Payload | Optional JSON seed data emitted when you run manually |

Use Sample Payload when downstream nodes expect data before you have a webhook or scheduled source. Top-level object fields are available directly, such as `{trigger.token}`. If you paste an array or primitive, the editor stores it wrapped as `{ "body": <value> }` and you access it via `{trigger.body}`.

Output [#output]

Every manual run emits at minimum:

```json
{
  "triggeredAt": "2026-05-14T10:00:00.000Z",
  "source": "manual"
}
```

With a Sample Payload such as `{ "token": "SOL", "amount": 1.5 }`, the trigger output becomes:

```json
{
  "token": "SOL",
  "amount": 1.5,
  "triggeredAt": "2026-05-14T10:00:00.000Z",
  "source": "manual"
}
```

Downstream nodes reference fields with the trigger response name (default `trigger`): `{trigger.token}`, `{trigger.triggeredAt}`, `{trigger.source}`. The base fields (`triggeredAt`, `source`) always win on key collision, so naming a payload field `source` is shadowed.

Running [#running]

Two ways to trigger a manual run:

1. **From the editor** - click the Run button in the top toolbar
2. **From the dashboard** - use the Run action on a workflow card

In execution history [#in-execution-history]

Manual runs show `manual` as the trigger source. They count toward your monthly execution limit.

Next steps [#next-steps]

* [Webhook Trigger](/docs/triggers/webhook) - automate with external events
* [Cron Trigger](/docs/triggers/cron) - automate on a schedule