Users
When using the "user" parameter in a JSON trigger, It it is only possible to include the userID, and in some limited cases a user type workflow parameter.
A JSON trigger action does not accept the Confluence userName.
...
The userId can also be added to the recipient parameter "recipients" parameter in the send-email trigger action.
Groups
When using the "group" parameter in a JSON trigger, you can include either the groupName and/or the groupID, and in some cases a group type workflow parameter.
...
- assign trigger action as approval reviewers assignees
- send-email trigger action as a value for
"recipients"
Workflow parameters
Workflow parameters defined in the workflow can be added to some trigger actions using the enclosed in the "@" operator.
...
| 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.