Manual Trigger Node

Start a workflow on-demand by providing static or dynamic output data.

The Manual Trigger node is the entry point for workflows that are started by a user clicking "Run" in the workflow builder. You configure an output value that is evaluated and passed to the next node in the workflow. The output can be a plain string, a JSON object, or a dynamic JavaScript expression that references workflow variables. This makes it the most flexible trigger for ad-hoc tasks, testing, and interactive workflows.

Parameters

Parameter	Type	Required	Default	Description
output	string	Yes	""	The data passed to downstream nodes. Supports fixed values and expressions.

Configuring This Node

When you select a Manual Trigger node, the configuration panel displays two sections from top to bottom:

1. Variable Selector — A multi-select dropdown at the top of the panel lets you bind workflow variables to this node. Select one or more variables to make them available in expressions. A "Create variable" button in the dropdown footer lets you define new workflow variables without leaving the panel — the new variable is immediately available for selection.

2. Output — A single text field where you enter the value the trigger will produce. A mode toggle on the field lets you switch between Fixed and Expression modes. These are the only two modes available for this parameter — there is no AI-decide or template mode.

Configuring the Output

The output field supports two input modes, selectable in the node configuration panel:

Fixed Mode (default)

Enter a static value — a plain string, a URL, a JSON object, or any text. The value is passed as-is to the next node.

Examples:

Value	Use case
https://example.com	Pass a URL for web scraping
John Doe	Pass a name for a research workflow
{"company": "Acme", "website": "https://acme.com"}	Pass structured data as JSON
@channel_handle	Pass a social media handle

Expression Mode

Switch the parameter mode to Expression to write a JavaScript expression that is evaluated at runtime. This lets you reference workflow variables and build dynamic outputs.

In expression mode, you have access to:

• variables — an object containing the values of all workflow variables you have selected for this node.

Examples:

Expression	Description
variables.targetUrl	Use a workflow variable as the output
`Hello, ${variables.userName}!`	Interpolate a variable into a string
JSON.stringify({ url: variables.siteUrl })	Build a JSON payload from variables

Workflow Variables

When using expression mode, you can bind workflow variables to the Manual Trigger node using the Variables selector at the top of the configuration panel. Only selected variables are available inside expressions.

Workflow variables are defined at the workflow level and can hold values of type string, number, boolean, or secret. They are useful for parameterizing workflows so the same workflow can be reused with different inputs without editing node configurations.

You can create new variables directly from the configuration panel by clicking the "Create variable" button in the variable selector dropdown. This is convenient when you realize mid-configuration that you need a new variable — you don't have to navigate away from the node panel.

How It Works

1. Add a Manual Trigger node as the first node in your workflow.
2. Configure the output field with a fixed value or an expression.
3. Optionally, select workflow variables to make them available in expressions.
4. Click Run (test or live) in the workflow builder to start the workflow.
5. The output value is evaluated and passed as the trigger output to the next node.

Examples

1. Pass a URL for Web Scraping

Provide a URL that a downstream Browse Web node can use.

Mode: Fixed

https://example.com/blog

2. Pass Structured JSON Data

Provide a JSON object with multiple fields for downstream processing.

Mode: Fixed

{
  "companyName": "Acme Corp",
  "website": "https://acme.com",
  "industry": "SaaS"
}

3. Dynamic Output from Variables

Use a workflow variable called targetUrl to make the trigger reusable.

Mode: Expression

variables.targetUrl;

4. Build a Prompt from Multiple Variables

Combine several workflow variables into a formatted string.

Mode: Expression

`Research ${variables.companyName} (${variables.website}) and summarize their product offerings.`;

Output Structure

The node outputs whatever value the output parameter evaluates to. If the output is a valid JSON string, downstream nodes receive the parsed JSON object. Otherwise, the raw string is passed through.

String output example:

"https://example.com"

JSON output example (when the fixed value is a valid JSON string):

{
  "companyName": "Acme Corp",
  "website": "https://acme.com"
}

Important Notes

• Empty output is valid: An empty string works when the workflow does not need initial input — for example, when the first action node fetches data from an external source on its own.
• Expression evaluation: Expressions run in a sandboxed JavaScript environment. Only the variables object is available — you cannot access external APIs or Node.js modules.
• Variable selection: You must explicitly select which workflow variables the node can access. Unselected variables are not available in expressions.
• Creating variables inline: Use the "Create variable" button in the variable selector to add new workflow variables without leaving the node configuration panel.
• Parameter modes: The output field supports only Fixed and Expression modes. Other modes (such as AI-decide or template) are not available on this node.
• JSON parsing: If the output string is valid JSON, it is automatically parsed into an object for downstream nodes. Non-JSON strings are passed through as plain text.
• Test vs. live runs: The Manual Trigger behaves the same in test and live runs. The only difference is that test runs are labeled as such in the run history.