Create an event-triggered task

Set event matching rules

Event details matching rule

System event details are JSON-formatted, with fields that vary by event type. Use these fields to filter events. For example, an ECS lifecycle state change event has the following `content` format:

{
    "resourceId": "i-bp1ecr********5go2go",  
    "resourceType": "ALIYUN::ECS::Instance", 
    "state": "Running"                       
}

In this example, `resourceId` is the ECS instance ID. The `state` field can be Pending, Starting, Running, Stopping, Stopped, or Deleted.

The matching rule is also JSON-formatted. Keys must match the event detail fields, and values specify conditions. To match a stopped instance:

{
  "state": "Stopped"
}

To match instance i-abcde being stopped or released:

{
  "resourceId": "i-abcde",
  "state": ["Stopped", "Deleted"]
}

Refer to the sample event message body on the page. The `content` section contains the event details.

Select a template

Select the template to run when the event occurs.

Set runtime parameters for the template

Template parameters accept static values or dynamic values from the event message body. If you enter static values, the template is always executed with those parameters. For dynamic values, use jq expressions to fetch fields from the message body.

Prefix dynamic values with $ followed by a jq expression. For example, use $.content.resourceId to fetch the `resourceId` from an ECS lifecycle state change event, or $.regionId for the region ID.

The event message body contains these fields:

Select parameters from the event message body:

For static values, set the parameters as you would for a regular template.