Ziflow events

Ziflow events are something that happens during the review of a proof, like a proof being created, a stage starting, or feedback being submitted. They start automation flows.

You can also start a flow using an intake form or a cloud storage event.

1. Open the Connect tab and select Create Flow.
   
   
    

2. In Choose Application, select Ziflow. 
   Note: If you do not see Ziflow, you need to connect the Ziflow application. See Connect your Ziflow app.

   These Ziflow events can be used to start your automation flow. 
    

• New proof/version

  An event is started by creation of a new proof or a new proof version.

  Field	Description
  Triggered by	Select the type of request(s) that will start the flow. New proof - started when the proof is fully uploaded New version - started when version is fully uploaded New proof in preparation - started when the proof begins preparing New version in preparation - started when version begins preparing Failed proof
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.
  Created by	Select the user responsible for this flow activation.
  Created from	Select a source location from which the flow will be started, such as an intake form or a project management tool.

   

• Proof updated

  An event is started by a proof update.

  Field	Description
  Triggered by	Select the type of request(s) that will start the flow. Changes to: Proof folder Proof settings Proof name Custom property Integration properties
  Modified in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• Proof trashed/restored

  An event is started by a proof being sent to the trash or restored from it.

  Field	Description
  Triggered by	Select the type of request(s) that will start the flow. When a proof: Is sent to the trash Is restored from the trash
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.
  Created by	Select the creator of the proofs you want to monitor.
  Created from	Select a source location from which the flow will be started, such as an intake form or a project management tool.

   

• Stage updated

  An event is started by updating a stage.

  Field	Description
  Triggered by	Select which type of the stage updated event should start the flow: Reviewer added Reviewer removed Stage locked Deadline changed
  Modified in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• Stage started

  An event is started by starting a stage.

  Field	Description
  Triggered by	Select which type of the stage updated event should start the flow: Automatically Immediately Manually
  Modified in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• Decision update

  An event is started by a decision.

  Field	Description
  Triggered by decision made	Select which level a decision needs to be made to start the flow: On a proof On a stage By a reviewer
  Type of decision	Choose the type of decision that needs to be made to activate the flow.
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• New comment/reply

  An event is started by a new comment or a reply.

  Field	Description
  Triggered by new comment / new reply	Select whether a comment or a new reply should start the flow.
  Made by	Choose if a specific reviewer or anyone who adds a comment/reply will activate the flow.
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• Comment resolved

  An event is started by a resolved comment.

  Field	Description
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• Comment labeled

  An event is started by a comment label.

  Field	Description
  Trigger by label made	Select whether this event should prompt action based on adding labels to comments, replies, or both.
  Comment is labeled as	Select which label(s) should start the flow.
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

   

• Comment reaction

  An event is started by a comment reaction.

  Field	Description
  Trigger by	Select whether to start a flow based on reactions added to comments, replies, or both.
  Comment reacted with	Select what type of reaction should start the flow.
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.

• Checklist results

  An event is started by a comment reaction.

  Field	Description
  Trigger by	Select whether to start a flow based on: The completion of an entire checklist  When any check item is selected.
  Made by	Select which checks start the flow: Anyone: Checks from any user or ReviewAI ReviewAI: Only ReviewAI checks Specific users: Specific user(s) checks
  Created in	Select the folder that this flow will monitor.  Any folder: The flow monitors all folders General workspace: Choose a specific folder (select General workspace text to open a drop-down list) that the flow monitors Include subfolders: Include subfolders so any proof created in any subfolder will also start the flow.