Skip to content
New AI Custom Form BuilderDescribe the intake form. It ships branded and end-to-end encrypted.AI Custom Form Builder is here See it build
Security

New Event Trigger: Add Recipient

SendSafely Actions just got more flexible. We’ve introduced a new event that triggers when a recipient is added to a transfer package or workspace.

Brian Holyfield · 2 min read
New Event Trigger: Add Recipient

SendSafely Actions just got more flexible. We’ve introduced a new event that triggers when a recipient is added to a transfer package or workspace.

Until now, Actions workflows were triggered by upload events like adding a file to Workspace or submitting a Dropzone or Send package. With this new event, you can now trigger workflow logic based on when a recipient is added to a package, unlocking new workflow possibilities for security and compliance teams.

Why this matters

Many organizations need to enforce policies based on who data is being shared with , not just who sends it. This is especially important for:

How it works

The new trigger event is automatically available for use from the SendSafely Actions page in the web portal and the API. If working with our API, you can learn more about the event payload, and available filters in our article here. Event Filters

Our new trigger event means you can now build workflows that react in real time as recipients are added, giving you more granular control over how data is shared.

SendSafely Actions is available on our Enterprise plan. Contact the SendSafely team today for a demo and discover how SendSafely Actions can streamline your operations while prioritizing security at every step.


SendSafely: Integrated File Transfer for the Apps you Love

If you are looking for a secure way to transfer files with customers or business partners, our platform might be right for you. Contact us today to request a demo and free trial subscription.

Request a Demo

Frequently asked questions

What is the Add Recipient trigger in SendSafely Actions?

It is a workflow trigger that fires when a recipient is added to a transfer package or Workspace. Before it was introduced in March 2026, SendSafely Actions workflows were triggered by upload events, such as adding a file to a Workspace or submitting a Dropzone or Send package.

How can SendSafely Actions support data loss prevention?

With the Add Recipient trigger, you can build workflows that run scans or block actions when sensitive files are shared with external recipients. Because the trigger fires as recipients are added, policies can be based on who data is shared with, not only who sends it.

Can SendSafely prevent sharing with restricted users or domains?

The Add Recipient trigger supports information barrier workflows that prevent sharing with restricted users, domains, or groups. You define the logic in a SendSafely Actions workflow, and it reacts in real time when a recipient is added to a package.

Where do I configure the Add Recipient trigger?

The trigger is automatically available on the SendSafely Actions page in the web portal and through the API. API users can find the event payload and available filters in SendSafely’s help center article on creating workflows with the Actions API.

Which SendSafely plan includes Actions?

SendSafely Actions is available on the Enterprise plan. Teams can contact SendSafely for a demo of how Actions workflows, including the Add Recipient trigger, fit their security and compliance processes.

Written by Brian Holyfield