...
When using the "user" parameter in a JSON trigger, it is only possible to include the userID, and in limited cases a user type workflow parameter.
A
JSON trigger
...
actions does not accept the Confluence userName.
In the example below, the assign trigger action uses the Confluence userID.
...
The "user" parameter is used in the following JSON trigger actions:
The userId can also be added to the "recipients" parameter in the send-email trigger action.
...
For trigger actions, the "group" parameter is only currently used in the
assign trigger action as approval reviewers assignees
send-email trigger action as a value for
"recipients"
...
Workflow parameters defined in the workflow can be added to some trigger actions using the enclosed in the "@" operator.
For triggers, a user or group type workflow parameter is only currently valid for use in the send-email trigger action as a value for "recipients".
| 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"}}
]}
] |
...
| Info |
|---|
If adding the JSON trigger using workflow builder there is no need to include the opening |