These components will allow you to effectively build your automations based on various types of events that could take place within the project. You can choose to send a webhook or email as a response to specific events, or use a custom action instead.

To learn more about creating automations, read here.


These are the ‘trigger’ components that your pipeline will look out for. When you choose an event as the trigger, it’ll mean that any time that event takes place in your project, the automation will be activated. If, for instance, you wanted to receive an email update if a particular folder had a status change, you could set up an automation for that.

Below are the available event components that could be used in your pipelines.


  • Project created
  • Project status updated
  • Project deleted


  • Folder created
  • Folder status updated
  • Folder deleted


  • Export created
  • Export status updated
  • Export deleted


  • Item created
  • Item opened in editor
  • Item annotation status updated
  • Item approval status updated
  • Item annotator assignment updated
  • Item QA assignment updated


Actions are the components you can use to define what takes place after an event has been triggered. You can choose to use the available actions provided, or build your own custom ones. When an action is carried out, it is logged in your pipeline's history. Learn more.

Below are the available action components that could be used in your pipelines.

Default actions

  • Send webhook
  • Send email

Custom actions
Here, you’ll see all the custom actions that you’ve created as individual action components that you can use in the canvas.