Setting Up a Manual Trigger

Configure a manual trigger to run your workflow on demand.

Overview

A manual trigger is the simplest way to start a workflow: you press Run and the workflow executes. There is no schedule, no inbound HTTP request, no inbox to poll. The workflow only runs when a person (or another workflow via a Subworkflow node) invokes it.

Manual triggers are the default choice while you are building and testing a workflow, and they remain useful in production for ad-hoc operations: rebuilding a report, kicking off a one-off data sync, replaying a failed job with new inputs. They also pair well with input variables, so the same workflow can be reused for different values without editing the definition.

Configuration

1. Click the Trigger node on your canvas.
2. In the properties panel, set the trigger type to Manual.
3. Optionally add input variables. For each variable, set a name, a type (string, number, boolean, JSON), and a default value if you want one.
4. Save the workflow.

Settings

• Trigger type - Set to Manual.
• Input variables - Optional list of named inputs the user supplies at run time. Each input becomes available downstream as {{ input.variableName }}.
• Default values - Pre-fill the run dialog so most runs only need a click.

Running a Manual Workflow

You can start a manual run from two places:

• Designer toolbar - Click Run while editing the workflow.
• Workflow list - Open the workflows page and click the run action on the workflow card.

If the trigger defines input variables, Spojit opens a dialog prompting for values before the run starts. Defaults are pre-filled; you can edit any field before confirming.

Example: Reusable Report Generator

Define a manual trigger with inputs startDate and endDate. Downstream nodes reference them as {{ input.startDate }} and {{ input.endDate }}. The same workflow now generates a report for any date range without editing the definition.

Tips

• Use input variables instead of hard-coding values. It makes the workflow reusable and testable.
• Set sensible defaults so a quick run requires zero typing.
• Manual triggers are the fastest way to test changes - save and click Run, no waiting for a schedule or webhook.
• If you find yourself running a manual workflow on a regular cadence, swap the trigger for a Schedule trigger.

Common Pitfalls

• Input typos - Variable names are case-sensitive. {{ input.UserId }} and {{ input.userId }} are different references.
• Missing required inputs - Inputs without defaults must be filled in the run dialog or the workflow fails immediately.
• Mistaking Manual for disabled - Manual workflows never auto-run, but they still count toward your plan limits once executed.
• Type mismatches - An input declared as number will reject a non-numeric value. Match types to how downstream nodes use the value.

Related Articles

• Setting Up a Schedule Trigger
• Setting Up a Webhook Trigger
• Setting Up an Email Trigger
• Working with Variables and Templates
• Running Your First Workflow

Learn More

• Trigger node documentation