- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Installing X-Pack
- Migrating to X-Pack
- Breaking Changes
- Breaking Changes in 5.5.2
- Breaking Changes in 5.5.0
- Breaking Changes in 5.3
- Breaking Changes in 5.2
- Breaking Changes in 5.0
- Breaking Changes in Shield 2.4.2
- Breaking Changes in Reporting 2.4.1
- Breaking Changes in Shield 2.4.0
- Breaking Changes in Shield 2.1.0
- Breaking Changes in Shield 2.0.1
- Breaking Changes in 2.0.0
- Breaking Changes in Shield 1.3.0
- X-Pack Settings
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing Elasticsearch and Kibana
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Limitations
- License Management
- Release Notes
WARNING: Version 5.5 of the Elastic Stack has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Simple Input
editSimple Input
editUse the simple
input to load static data into the execution
context when the watch is triggered. This enables you to store the data
centrally and reference it with templates.
You can define the static data as a string (str
), numeric value (num
), or
an object (obj
):
"input" : { "simple" : { "str" : "val1", "num" : 23, "obj" : { "str" : "val2" } } }
For example, the following watch uses the simple
input to set the recipient
name for a daily reminder email:
{ "trigger" : { "schedule" : { "daily" : { "at" : "noon" } } }, "input" : { "simple" : { "name" : "John" } }, "actions" : { "reminder_email" : { "email" : { "to" : "to@host.domain", "subject" : "Reminder", "body" : "Dear {{ctx.payload.name}}, by the time you read these lines, I'll be gone" } } } }
Was this helpful?
Thank you for your feedback.