SendSafely Actions Overview

The SendSafely Actions framework enables you to build workflows that automate tasks in response to user activity within SendSafely. Actions are event-driven: you can trigger an action or series of actions–a workflow–when a specified event occurs. A couple examples:

1. Every time someone uploads a file to a Dropzone, you can block access to that file and automatically analyze it using your own antivirus software before unblocking access.
2. Any time anyone sends a file, you can notify your own archiving system to capture a copy for compliance purposes.

A workflow consists of one or more actions and is triggered by an event. 

• Workflows can be created by end users (Personal Workflows) or by enterprise admins at the organization level (Enterprise Workflows). Enterprise workflows can only be viewed/edited by an admin. 
• Personal Workflows can only be triggered by events related to the user who owns the Workflow, while Enterprise Workflows can be triggered by events related to any or all users in the Organization. 

An event is a specific activity that triggers a workflow. We'll be adding more over time, but currently support the following events:

1. Uploading a file to a Workspace
2. Finalizing a Transfer or Dropzone package

Event Filters allow you to execute a workflow only when events match certain criteria. Every event has a set of properties that can be used to build an event filter. For example, you can trigger a workflow only when a certain user finalizes a package, or only when a file is uploaded to a specific workspace. 

Enterprise workflows don't have default filters, but personal workflows include a default filter based on the packageOwner attribute. This default filter can't be edited, and prevents users from triggering workflows on items that don't belong to them.

Actions represent specific steps that execute in response to the event. A workflow can have multiple actions, which are executed in order (referred to as steps in the workflow). For example, a workflow might:

• Step 1. Block access to a package.
• Step 2. Scan the package for malware.
• Step 3/4. Unblock or delete the package based on the results of the scan. 

Action Filters, similar to event filters, can be used to define criteria that must be met for specific steps of the workflow to run. In the previous example, you'd define actions with filters that unblock the package if the malware scan returns a clean result, and delete the package if malware is detected:

To learn how to create and monitor Actions workflows, proceed to this help center article.