Manual triggers
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
GA
9.4+
…
Generally available since 9.4
Preview in 9.3
Manual triggers run workflows on-demand through the UI or API. They require explicit user action to start a workflow. Use manual triggers for testing, one-off tasks, administrative actions, or workflows that require a human decision to start.
Manual runs use the privileges of the user who starts the run. For details, refer to Workflow authorization.
To define a manual trigger, use the following syntax:
triggers:
- type: manual
This allows you to run a workflow manually by:
- Clicking Run in the Workflows UI
- Calling the workflow execution API, either directly or from an external system
Manual triggers can accept input parameters, which you can reference in any step. When you define inputs at the workflow level, users are prompted to provide values when they run the workflow.
Refer to Pass data and handle errors > Choose between constants and inputs to learn when to use inputs or constants in workflows.
name: Manual Processing Workflow
inputs:
- name: environment
type: string
required: true
default: "staging"
description: "Target environment for processing"
- name: batchSize
type: number
required: false
default: 100
description: "Number of records to process"
- name: dryRun
type: boolean
required: false
default: true
description: "Run in test mode without making changes"
triggers:
- type: manual
steps:
- name: validateInputs
type: console
with:
message: |
Starting workflow with:
- Environment: {{ inputs.environment }}
- Batch Size: {{ inputs.batchSize }}
- Dry Run: {{ inputs.dryRun }}