...
In the example below, the assign trigger action uses the Confluence userID.
| Code Block |
|---|
"triggers":" [ {"event": "on-change-state", "conditions": [ {"state": "Review"} ], "actions": [ {"action": "assign", "approval": "Teamreview", "user": "5d52a37ef0f22a0da2d6f070"} ]} ] |
...
| Code Block |
|---|
"triggers":
[
{"event": "on-change-state",
"conditions":
[
{"state": "Approved"}
],
"actions":
[
{"action": "send-email",
"recipients":
[
"@creator",
"@my_project_team@",
"@my_QA_leader@"
],
"notification": {"subject": "${content.title} is in the Approved published state",
"title": "${content.title} is in the Approved published state",
"body": "Hello, ${content.link} in the ${content.space} space is in the Approved published state"}}
]}
] |
If adding the JSON trigger using workflow builder there is no need to include the opening "triggers": JSON markup notation, since it will be added by workflow builder.