...
In case a push event is a workflow event (pipeforce.event.workflow.#), these additional address variables can be used in TO, CC and BCC fields to refer to data from the event message:
$uri:wf-authenticated-user= Returns the$uri:user:<username>of the user who was logged-in at the time of this event and potentially has initiated this event.$uri:wf-process-involved-users= Returns the$uri:user:<username>of all users involved in the workflow process.$uri:wf-started-by= Returns the$uri:user:<username>of the user who started the workflow.$uri:wf-task-candidate-groups= Returns the$uri:group:<name>names of all groups which are set as candidate group of given task. In case there is no candidate group set, the address variable will be removed from all address fields.$uri:wf-task-assignee= Returns the$uri:user:<username>of the user who is set as assignee on given workflow task. In case there is no taskAssignee set, the address variable will be removed from all address fields.$uri:wf-task-owner= Returns the$uri:user:<username>of the user who is set as assignee on the given workflow task. In case there is no taskOwner set, the address variable will be removed from all address fields.
...