Trigger a webhook when a file arrives
The Event Manager turns an upload into an action. In the WebAdmin UI, open Event Rules and add a rule. Choose the trigger, for example File Uploaded, set the conditions such as a name pattern or a target folder, and add an HTTP action pointing at your webhook URL. Every matching upload now posts a J
The Event Manager turns an upload into an action. In the WebAdmin UI, open Event Rules and add a rule. Choose the trigger, for example File Uploaded, set the conditions such as a name pattern or a target folder, and add an HTTP action pointing at your webhook URL. Every matching upload now posts a JSON payload with the file name, path, size, and the user who sent it.
A common pairing is an n8n workflow: the webhook starts the flow, the flow moves the file, writes a database row, or notifies a channel. Because the payload includes the user and the path, one workflow can route drops from many partner folders differently. Conditions, actions, and template variables such as the file name are available without any server-side configuration.
Actions can also be filesystem operations, copy to another folder, delete after a retention period, rename into a processed directory, or send an email. The community edition covers triggers, conditions on names and paths, and these actions; advanced multi-step orchestration is part of the Enterprise edition.
