Message Rules|pushplus

"Serialized Data" is usually enough: enter the field name as the key. When the request body is JSON, you can use a dot path such as alerts.0.job.

For the Message API, values come from the "Request Headers / Query / Request Body" source.

Extraction Method	Key / Expression Example
Serialized Data	`status`、`User-Agent`
Regular Expression	`errorCode=(\d+)`
JSONPath	`$.alerts[0].job`
Raw Text	Leave empty to take the whole request body

Variable names must be unique; templates and conditions use {{varName}} to get a single value. If the query and request body have fields with the same name, name them separately, e.g. queryA / bodyA; the keys can still be the original field name.

Built-in title and content: the Query value is used if present, otherwise the Body field with the same name. If both exist, Query wins; to read the Body field separately, add your own template variable.

Emails sent to {token}@yp9.cn enter the rules. Custom variables are extracted from the "Subject" or "Email Body" source.

Source	Extraction Method	Description
Subject	Raw Text	Takes the whole email subject
Subject	Regular Expression	Extracts a field from the subject, e.g. `DiskAlert\s+(\S+)`
Email Body	Serialized Data / JSONPath	When the body is JSON, enter the field name, e.g. `status`, `$.alerts[0].job`
Email Body	Regex / Raw Text	Matches within the body, or takes the whole body

Sender, recipient, CC and token are built-in variables from, to, cc and token; no extraction needed.

Built-in title and subject are the subject; content and body are the body. They will not conflict with same-named fields in the JSON body.

The default value is used when nothing is extracted. Extracted values can be referenced with {{varName}} in the message title, content, template and trigger conditions. Variable names must be unique.

QR code expired. Click to refresh

New Message Rule

Product

Support

Follow Us