Trigger deployments

A trigger deployment runs a workflow when a certain event occurs. For example, when a new file is added in a folder.

Before you start

You need:

• Edit right on a team space

Step 1 — Create a version

You can only create deployments from a version of the workflow. See Create a version.

Step 2 — Create the trigger deployment

1. On the workflow page, click Deploy → Trigger.
2. Enter a deployment name.
3. Select the workflow version.
4. Select an environment.
5. Enable the desired email notifications.
6. Select the deployment execution scope.
7. Set the configuration options

Step 3 - Configure the trigger

Define the events that trigger the workflow execution.

1. Select a team and a space. You can only select teams and spaces you have access to.
2. Select an item type, file or folder.
3. If the trigger is on files, select the file type.
4. Select an action. For example, trigger the execution when a new file is created, or when a folder is deleted.
5. Optionally select additional filtering in a subfolder of the space.

Pause and resume

From the deployment list, you can stop and resume the trigger deployment without deleting it. A deployment runs automatically only when it is enabled.

Update the deployment

Deployments are pinned to a specific workflow version, and a trigger runs when specific events occur. You can change either without creating a new deployment.

To change the workflow version:

1. Make your changes in the editor.
2. Create a new version.
3. Open the deployment settings and select the new version.

The deployment picks up the updated workflow on its next trigger.

To change when the trigger runs, open the deployment settings and edit the trigger options. Changes take effect on the next triggered execution.