Start free

Manual Run

The Manual Run trigger fires when you click the Run button in the canvas toolbar. No external event needed; you control when it runs.

Internal name: Input Setup Node color: Navy (#1C3693)

Setting it up

  1. Click the Trigger Setup node

  2. Select Schedule & Manual → Manual Run

  3. Optionally define input parameters

  4. Click Save & Close

This is the simplest trigger: selecting it is all that's needed. No webhooks to set up, no schedules to configure.

Input parameters (optional)

You can define expected input parameters that are passed when the workflow runs. This is useful for workflows that need different data each time.

The Input Schema editor lets you define key-value pairs:

ColumnDescription
KeyParameter name (e.g., email, customer_id)
TypeData type (string, number, boolean, etc.)

When you run the workflow, you'll be prompted to fill in these parameters. They become available as variables: {{trigger.email}}, {{trigger.customer_id}}.

If you don't define any parameters, the trigger produces an empty output; downstream nodes won't have trigger variables to reference.

When to use Manual Run

  • Testing: build your workflow with manual trigger, then swap to webhook/schedule when ready
  • One-off tasks: run a data migration, cleanup, or report on demand
  • Demos: show a workflow working without waiting for real events
  • API-triggered: trigger the workflow programmatically via the TinyCommand API

Running a manual workflow

Click the Run button (▶️) in the bottom toolbar. If you defined input parameters, a form appears asking you to fill them in. Otherwise, the workflow runs immediately.

Tip

Manual triggers are ideal for prototyping. Build your entire workflow with Manual Run, test it thoroughly, then swap the trigger to Webhook or Schedule for production.

Note

Manual triggers can also be invoked via the TinyCommand API, making them useful for workflows triggered by external systems that don't support webhooks.

Error handling

If this node fails during execution:

  1. The execution stops at this node (unless Continue on error is enabled)
  2. The error appears in the Execution History with the full error message
  3. Downstream nodes don't execute

To handle errors gracefully:

  • Enable Continue on error in the node settings
  • Add an If-Else node after to check if the operation succeeded
  • Route failures to a notification (Send Email, Send Slack)

Debugging

  1. Check the Execution History for the failed run
  2. Click the failed node to see its input and error
  3. Verify the input data is correct (check previous node outputs)
  4. Test with sample data using the Test tab