> ## 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.

# Site Online

> Trigger when a site comes back online and resumes sending heartbeats.

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

* Auto-close outage alerts after site heartbeat recovery.
* Kick off post-recovery validation checks.

## Configuration Checklist

1. Trigger on Site Online to process recovery automation.
2. Fetch site metadata and verify post-recovery state.
3. Resolve or annotate active incidents.
4. Notify stakeholders that service is restored.

## 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.