Unified Trigger Model

Opscotch supports multiple trigger types that initiate execution without introducing new paradigms.

• HTTP-triggered steps
• File-based triggers
• Cron-like scheduled execution
• Step-to-step invocation

Real products require diverse execution entry points. Fragmented trigger systems create inconsistent architecture.

Opscotch routes all triggers into the same step composition model, preserving conceptual simplicity.

Triggers invoke a designated step, which then composes behavior through explicit step calls.

• External triggers route into steps
• Internal step invocation continues flow
• Background execution via fire-and-forget calls

A unified trigger model simplifies product design and reduces architectural complexity across deployment environments.