Page Comparison

The trigger action "send-email" sends a custom email to one or more specified recipients. 

• action (send-email)

• recipients (array) ❗️Recipients to send the email to (at least one recipient value must be added). A comma separated list of one or more recipients or Confluence groups is added using:

  • one or more Atlassian userIDs Email addresses

  • one or more user type workflow parameter referencesobjects by specifying the Atlassian userIDs

  • one or more group objects by specifying Atlassian groupIDs one or more the Atlassian groupNames

  • one or more group user type  parameters (see workflow parameter references)

  • one or more Email addresses group type parameters (see workflow parameter references)

  • One or more of the following value references can also be added as a value for the "send-email" action "recipients"

    • @watchers  Note that @watchers refers to the watchers set at a document level, not including the watchers of the space

    • @lastUpdatedBy

    • @creator

• notification (object) ❗️ Notification holder. Can include the following You must include at least an email "subject" and "body" ("title" is optional), as a comma-separated list within curly brackets :

  • the email "subject"

  • "title"

  • "body"

  emailContext (object) Email context object(and you could even embed any of the following as part of the notification text: ${content.title} | ${content.link} | ${content.space} 

  These can be used in the

  ):

  • "subject",

  • "title" and "body" parameter values. You must include an email "subject" value and

  • "body" value

❗️Mandatory parameters - at least one value for "recipients" must be specified and the "notification" holder must include at least one of "subject", "title", or "body"

"triggers":
[
	{"event": "on-change-state",
	"conditions":
	[
		{"state": "Review"}
	],
	"actions":
	[
		{"action": "send-email",
			"recipients":
			[
				"@creator",
				"@watchers",
				"@lastUpdatedBy",
				"@document_user_reviewers@",
				"@document_group_reviewers@"
			
            [
                "email_1@email.com", "email_2@email.com",
                {"user": "user_ID_1"}, {"user": "user_ID_2"},
                {"group": "group_ID_1"}, {"group": "group_ID_2"},
                {"group": "group_Name_1"}, {"group": "group_Name_2"},
                "@user_type_parameter_1@", "@user_type_parameter_2@",
                "@group_type_parameter_1@", "@group_type_parameter_2@",
                "@creator",
                "@watchers",
                "@lastUpdatedBy"
            ],
			"notification": {"subject": "${content.title} is In Review State",
				"title": "${content.title} is In Review State",
				"body": "Hello, ${content.link} in the ${content.space} space is in approvalreview state. andPlease, needstake toa belook reviewed!"}}
	]}
]

  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.

 On-screen notification messages can be created using the "set-message" trigger action.

Workflow trigger-generated email 'failure to send' errors are included in the Confluence log.