Triggers

Triggers automate the launch of SchemAlign pipelines. Instead of requiring every run to be started manually from the Workspace, triggers define when and how a pipeline should begin.

SchemAlign trigger patterns include:

Scheduled triggers

Run a pipeline on a defined cadence, such as hourly, nightly, weekly, or after a business process window.

HTTP triggers

Expose a controlled endpoint that can launch a pipeline when an approved external system calls it.

Future event triggers

Reserve room for future event-based patterns, such as storage changes, upstream notifications, or application events.

When to use triggers

Use a trigger when a pipeline has a repeatable operational purpose:

• nightly data movement
• identity or account lifecycle workflows
• scheduled report extraction
• periodic validation jobs
• event-driven integrations started by a trusted system

Trigger safety

Triggers should be treated as operational automation, not just shortcuts. Before enabling a trigger, confirm that:

• the target pipeline has been tested manually
• credentials and service accounts are configured correctly
• expected outputs are stored in the right place
• failures will be visible in Overview and run history
• the schedule or HTTP access pattern will not overload source or destination systems

Do not use triggers to bypass review

A trigger should automate an approved pipeline. It should not be used to launch unreviewed destructive writes, untested custom node code, or pipelines that still require manual validation.