> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Reference for workflow trigger nodes, including scheduling, event-driven triggers, and synchronous API-triggered execution.

Trigger nodes start workflow execution. Every workflow must define exactly one trigger that determines when and how a run begins.

## How To Use Trigger Nodes

1. Choose one trigger only for the workflow entry point.
2. Configure trigger-specific parameters (schedule, event source, or API mode).
3. Connect trigger output to the first processing step.
4. Test with representative payloads and verify downstream context values.

## Choosing The Right Trigger

* Use **Scheduled Trigger** for recurring maintenance and reporting.
* Use **API Trigger (Synchronous)** when another system must invoke workflow execution directly.
* Use **SNS-based lifecycle/health triggers** for event-driven automation from platform signals.
* Use **Workflow Trigger** to create reusable callable sub-workflows.

## Trigger Types

<CardGroup cols={2}>
  <Card title="Manual Trigger" icon="mouse-pointer-click">
    Start this workflow via an API call or the UI.

    [View](./trigger)
  </Card>

  <Card title="Trigger by Another Workflow" icon="waypoints">
    Call this workflow from another workflow.

    [View](./workflow-trigger)
  </Card>

  <Card title="Scheduled Trigger" icon="calendar-clock">
    Run this workflow on a recurring schedule.

    [View](./scheduled-trigger)
  </Card>

  <Card title="API Trigger (Synchronous)" icon="globe">
    Trigger this workflow via API call with synchronous execution.

    [View](./sync-request-trigger)
  </Card>

  <Card title="Site Added" icon="map-pin-plus">
    Trigger this workflow when a new site is added.

    [View](./site-added)
  </Card>

  <Card title="Site Removed" icon="map-pin-minus">
    Trigger this workflow when a site is removed.

    [View](./site-removed)
  </Card>

  <Card title="WAN Interface Offline" icon="wifi-off">
    Trigger when a WAN interface from a WAN failover goes offline.

    [View](./wan-offline)
  </Card>

  <Card title="WAN Packet Loss" icon="cloud-alert">
    Trigger when a WAN interface from a WAN failover experiences packet loss.

    [View](./wan-packet-loss)
  </Card>

  <Card title="WAN Packet Loss Resolved" icon="cloud-check">
    Trigger when a WAN interface from a WAN failover recovers from packet loss.

    [View](./wan-packet-loss-resolved)
  </Card>

  <Card title="WAN Interface Online" icon="wifi">
    Trigger when a WAN interface from a WAN failover comes online.

    [View](./wan-online)
  </Card>

  <Card title="Site Offline" icon="triangle-alert">
    Trigger when a site fails to check in with the management system for more than 5 minutes.

    [View](./site-offline)
  </Card>

  <Card title="Site Online" icon="check">
    Trigger when a site comes back online and resumes sending heartbeats.

    [View](./site-online)
  </Card>
</CardGroup>

## Registry-Only Trigger Entries

These exist in the automation registry but are excluded from prompt-assistant context (for example, subflow-only nodes).

<CardGroup cols={2}>
  <Card title="Subflow Trigger" icon="workflow">
    This trigger is activated when a subflow is called.

    [View](./workflow-trigger)
  </Card>
</CardGroup>

## Trigger Design Best Practices

* Keep trigger configuration minimal and deterministic.
* Validate expected input schema before downstream processing.
* Add guard conditions early when trigger payloads can vary.
* Monitor missed or delayed executions for schedules and external callbacks.