Workflow trigger

Overview

A workflow trigger creates a more flexible and responsive workflow, adding custom automation to your documentation process.

When a selected event or action occurs, such as assigning a reviewer or changing the workflow state, you can use a workflow trigger to undertake one or more actions, such as changing the state or completing an approval.

One or more workflow triggers can be added to a custom workflow.

Graphic flowchart showing workflow trigger to automatically transition to a state on a state change

In the example above:

  • the trigger listens for a change of state

  • the condition constrains the trigger to listen for the state change to the Rejected state

  • once this event occurs, the trigger actions an immediate transition to the Draft state, ready to be updated by your editors

A trigger can be set to listen to one of a range of workflow events, including approval, reviewer assignment, and change of state events.

You can constrain the events by adding a condition for the event, such as a named state in the workflow.

One or more trigger actions can be added for a trigger. These actions include changing the state, sending a custom email, or removing page-level Confluence restrictions.†

Adding a trigger

A space administrator can add one or more triggers to a custom workflow using the visual editor.

image-20241217-183304.png

Triggers added to a workflow are shown in the workflow panel in the visual editor.

You can also add a trigger to a workflow using the code editor.

† Only 'Confluence Cloud Standard, Premium, and Enterprise Plans' enable customers to edit permissions, including global, space, and page permissions

Related pages