TotalApp Docs
Ctrl K
Home
EN | TR
Go to App

Triggers

Start a workflow on a schedule, an incoming webhook, a manual click, or an upstream data change.

Overview

The Triggers group holds every node that can start a workflow run. A workflow needs at least one trigger node before it can execute on its own; without one, it can still be run manually from the editor toolbar.

Trigger nodes have no incoming connections — they are always the entry point of a pipeline and appear at the far left of the canvas.

Nodes in This Group

NodeDescription
ScheduleRuns the workflow automatically on a recurring cron-style schedule (e.g. every day at 9am).
WebhookStarts the workflow when TotalApp receives an HTTP request at a generated webhook URL — ideal for reacting to external events.
ManualA trigger placeholder for workflows that are only ever started by clicking Run in the editor.
Data ChangeFires when a watched data source (e.g. a table or record) changes.
Linear WebhookStarts the workflow when a Linear issue event (created, updated, status changed) is received.

Usage Tips

One trigger per workflow (usually)

Most workflows use a single trigger node. If you need a pipeline to start from multiple different events, build separate workflows that share downstream logic via sub-workflows or a common integration node, rather than combining several triggers into one canvas.

Webhook URLs

Adding a Webhook trigger node generates a unique URL you can copy from the node's configuration panel. Any HTTP POST to that URL starts the workflow, with the request body available to downstream nodes.

Frequently Asked Questions

Can I test a workflow without waiting for its trigger to fire?
Yes. Use the Run button in the editor toolbar to execute the workflow immediately regardless of which trigger node it contains.
What happens if a workflow has no trigger node?
It can still be built and run manually, but it will not execute automatically — add a Schedule or Webhook trigger if you need the workflow to run unattended.