Type to search.

Streams action steps

Serverless Preview

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Preview

    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.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack Preview 9.4+

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Preview since 9.4

    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.

Streams action steps operate on Observability Streams from a workflow. Use them to list available streams, fetch a specific stream's configuration, or pull significant events from a stream's time window.

Warning

Streams action steps, along with the Streams feature itself, are in technical preview. Schemas and semantics can change in future releases. Use these steps for prototypes and investigation workflows; hold off on critical automation until Streams reaches GA.

Schema convention. In each schema table on this page, the Location column indicates where each parameter sits in the YAML:

  • top level: Alongside type and name, at the top of the step or trigger definition.
  • `with`: Inside the step's with: block.
  • `on`: Inside the trigger's on: block.

List every available stream in the current Kibana space. This step takes no parameters.

YAML 
- name: list_streams
  type: kibana.streams.list

Fetch a stream by name. The name is the human-readable stream identifier shown in the Kibana UI.

Parameter Location Type Required Description
name with string Yes Stream name.
YAML 
- name: get_logs_stream
  type: kibana.streams.get
  with:
    name: "logs-default"

Fetch significant events from a stream in a specified time range, optionally filtered by a query.

Parameter Location Type Required Description
name with string Yes Stream name.
from with string No Start of the time range. Accepts ISO timestamps (2026-04-01T00:00:00Z) or relative values (now-1h).
to with string No End of the time range.
bucketSize with string No Aggregation bucket size.
query with string No Filter query.
YAML 
- name: recent_significant_events
  type: kibana.streams.getSignificantEvents
  with:
    name: "logs-default"
    from: "now-1h"
    to: "now"