Workflow Templates
Use this page to decide between prebuilt templates and custom workflows.
What this page covers
- How to choose a template vs custom
- What each template is best for
- Where to find step-by-step implementation
When to start with a template
Start with a template when your use case matches a common pattern and you want faster delivery with lower configuration risk.
When to start custom
Start custom when branch logic, payload shape, or compliance behavior is unique to your domain and cannot be represented by a standard template pattern.
Template selection flow
Available template patterns
Shipped Basic starters in the template gallery also include patterns such as Echo / Passthrough (HTTP trigger), Manual trigger + echo (manual_trigger → Set → Response), Cron trigger + echo (cron_trigger → Code), and Kafka consumer + echo (kafka_consumer → Code).
- The manual template runs only from Execute workflow in the builder; see Manual Trigger.
- The cron template runs on schedule via the workflow scheduler; see Cron Trigger.
- The Kafka consumer template runs from consumed Kafka messages; see Kafka Consumer.
Implementation path
For detailed build/test/publish steps, open any template from the workflow canvas and select Use template to load it into a proxy's workflow editor.