# Manual trigger - Workflow trigger | Docs - nodulz

Source: https://nodulz.com/docs/nodes/manual

Language: en

Starts the workflow from the editor Run button

## Usage and specifics

Use this trigger to build a workflow with controlled data and no external connection. In **Test payload**, enter a JSON object such as:

```json
{
  "email": "ada@example.test",
  "amount": 120
}
```

Later steps read `{{ input.email }}` and `{{ input.amount }}`. The trigger output also contains `trigger`, `triggeredAt` and `payload`, but `input` refers directly to your object, with no `body` wrapper.

An empty payload gives empty input. An array or primitive value is wrapped under `input.value`. Use an object to follow [Getting started](/docs/getting-started).

Technical type : `manual`. Runtime : `nodulz`.

## Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the [credentials guide](/docs/credentials) if a remote source or execution target requires access.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `testPayload` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `testPayload`<br>Test payload | JSON injected as workflow input during a manual run. Example: a JSON object with a message field - read it as {{ input.message }}. |

## Examples

- Example payload with title My test - read {{ input.title }} in downstream nodes.

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "testPayload": ""
}
```

## Verification

Run with the payload above, then check `payload.email` in the trigger output and `{{ input.email }}` in a downstream Edit fields node. Change the amount and run again to verify the new execution’s data is used. This trigger tests processing; it does not verify delivery of a webhook or provider event.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)