Skip to main content

Start

The Start trigger is the manual entry point of a workflow — it begins execution on demand rather than in response to a schedule or an external event. It takes no configuration and no inbound payload: it simply marks where a run begins. Use it for workflows you launch yourself (testing, ad-hoc jobs, one-off runs) and as the default starting point while you build and iterate.

Overview​

Use the Start trigger when you need to:

  • Run a workflow on demand - Launch from the Splice editor whenever you choose, with no schedule or external caller
  • Develop and test - Validate workflow logic interactively as you build it
  • Handle one-off jobs - Data migrations, cleanups, backfills, and other tasks that run when you decide
  • Process accumulated work - Kick off a batch when the data is ready, rather than on a fixed cadence

Configuration​

The Start trigger has no parameters. Add it to a workflow and connect its output to the first node you want to run.

Output​

The Start trigger emits a single output keyed by the node's name. Because there is no caller and no inbound message, the trigger carries no payload — a Start run initiates work rather than delivering data into it. If a run needs initial values, set them in a downstream node (for example, a Set or Code node) right after Start.

Example Usage & Common Use Cases​

On-Demand Job​

[Start] → [HTTP Request: export records] → [Spreadsheet: build file] → [FTP: upload]

Building and Testing a Workflow​

Drop a Start node in front of the logic you are developing and run it from the editor to exercise each node with sample data before wiring up a real trigger.

Seed Initial Values​

[Start] → [Set: define run parameters] → [Loop: process items]

When to Use a Different Trigger​

Start is for manual, on-demand runs. Choose another trigger when the workflow should begin automatically:

Best Practices​

  • Use Start while iterating - It is the simplest way to run a workflow repeatedly during development.
  • Swap in an automated trigger for production - Once the logic is proven, replace or supplement Start with the trigger that matches how the workflow should actually begin.
  • Set initial state explicitly - Since Start delivers no data, define any required starting values in the first downstream node so the workflow's inputs are clear.

Troubleshooting​

Common Issues​

  • Workflow won't start automatically - Start is a manual trigger; it only runs when you launch it. Use Cron or Webhook for unattended execution.
  • Downstream node has no input - Start carries no payload. Provide initial values in a Set/Code node after Start.
  • Cron - Run a workflow on a time-based schedule
  • Webhook - Start a workflow from an inbound HTTP request
  • Trigger Nodes - Overview of all available workflow trigger types