Page Comparison

...

the on-approve event
the state condition to specify the approval state
the send-email action

The on-reject event is used for a separate event if an action is required on a user rejection decision.

Code Block

"triggers":
[
  {
    "event":"on-approve",
    "conditions":
	[
      {
        "state":"Review"
      }
    ],
    "actions":[
      {
        "action":"send-email",
        "recipients":[
          "@creator"
        ],
        "notification":{
          "subject":"${content.title} has been approved",
          "title":"${content.title} has been approved",
          "body":"Hello, ${content.link} in the ${content.space} has been approved by one approver"
        }
      }
    ]
  },
]

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.

event	on-approve	trigger will only listen for a user approve decision - condition added to constrain the event to the Review state
condition	state:Review	state condition for the trigger event
action	send-email	email sent to the content author (`@creator`). An email is sent for each approval decision by a user

...

title	JSON format to add to workflow builder

...

by

...

a user

...

on-approve and on-reject multiple event trigger

Code Block

"triggers":
[
  {
    "event":"on-approve",
    "conditions":[
      {
        "state":"Review"
      }
    ],
    "actions":[
      {
        "action":"send-email",
        "recipients":[
          "@creator"
        ],
        "notification":{
          "subject":"${content.title} has been approved",
          "title":"${content.title} has been approved",
          "body":"Hello, ${content.link} in the ${content.space} has been approved by one approver"
        }
      }
    ]
  },
  {
    "event":"on-reject",
    "conditions":[
      {
        "state":"Review"
      }
    ],
    "actions":[
      {
        "action":"send-email",
        "recipients":[
          "@creator"
        ],
        "notification":{
          "subject":"${content.title} has been rejected",
          "title":"${content.title} has been rejected",
          "body":"Hello, ${content.link} in the ${content.space} has been rejected by one approver"
        }
      }
    ]
  }
]

JSON format to add to workflow builder

Code Block

[{"event":"on-approve","conditions":[{"state":"Review"}],"actions":[{"action":"send-email","recipients":["@creator"],"notification":{"subject":"${content.title} has been approved","title":"${content.title} has been approved","body":"Hello, ${content.link} in the ${content.space} has been approved by one approver"}}]}, {"event":"on-reject","conditions":[{"state":"Review"}],"actions":[{"action":"send-email","recipients":["@creator"],"notification":{"subject":"${content.title} has been rejected","title":"${content.title} has been rejected","body":"Hello, ${content.link} in the ${content.space} has been rejected by one approver"}}]}]

It is mandatory in the send-email trigger action to add at least one recipient and include notification with subject and body values

A range of JSON trigger actions is available including the set-message action.

List of trigger actions

...

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.

Versions Compared

Old Version 1

New Version 2

Key

on-approve and on-reject multiple event trigger