Skip to main content
Triggers start workflow execution. A valid workflow should have exactly one trigger node. This trigger is the entry point for a workflow run and should be connected to the first downstream action or condition.

​
When To Use

  • Validate WAN performance immediately after link recovery.
  • Resume paused automations after connectivity returns.

​
Configuration Checklist

  1. Use WAN Interface Online to react to service restoration.
  2. Add verification steps (health or latency checks).
  3. Branch based on whether post-recovery checks pass.
  4. Send success or follow-up troubleshooting notifications.

​
Inputs

  • Node metadata in node.data: uiId and componentId.
  • Trigger-specific configuration from the node form (for example schedule or API trigger settings).
  • No upstream node input is required because this is the workflow entrypoint.

​
Outputs

  • Produces the initial workflow context (the trigger payload) for downstream nodes.
  • Exposes trigger/event data that subsequent actions and conditions can reference.
  • Starts execution flow for connected nodes.

​
Failure Modes

  • Missing or invalid trigger configuration fields.
  • Workflow disabled/inactive, so the trigger does not execute.
  • Event payload missing fields expected by downstream nodes.
  • Permission/integration issues that prevent trigger invocation.

​
Best Practices

  • Place this as the first node and connect it to the first action or condition.
  • Keep trigger payload shape stable so downstream mappings remain reliable.