Create a trigger

Create a files trigger — pick the event and the folder, then the action (send an email, push or SMS, call a webhook, run code, send an in-app event).

Where: Files → Triggers → Add New · /projects/<project>/files/triggers/new

Before you start

• For Send Email: the Email module is on, with an email template and an email integration (every project gets the Fake one, Test Me). For Send Push Notification / Send SMS: the same in that module. For Call Webhook: a destination in Project → Settings → Webhooks.

• To pick a folder from a list, the project needs a files integration with that folder — see Browser. You can also type the folder.

Steps

1. Press Add New. Under If this → Select trigger actions, pick the event: When uploaded or When deleted. The box below tells you what the action gets (Usage: 'New.File.*'). Under In this folder, type a folder or pick it in the list below the field (Every file, catalog, mugs, …), for example catalog. Only files in this folder and its subfolders fire the trigger; leave it empty to react to every file. Add activation code adds code that runs first and can stop the trigger.

   

   The event and the folder.
2. Under ... then, open the action list and pick the action.

   

   The action list.

   Action	What it does
   Run Code	Invokes a serverless function with the event data.
   Send Email / Send Push Notification / Send SMS	Sends a template to the recipients you choose.
   Call Webhook	POSTs a signed event (files.file.uploaded or files.file.deleted) to the destinations you tick. Save stays off until you tick an enabled destination subscribed to that event.
   Send In-App (Realtime / SSE)	Sends the event live to connected apps or AI agents.

3. For Send Email, choose Email Addresses and type the address in To: *, for example [e-mail]. Single email strategy sends each address its own email; CC: and BCC: are optional. Under Template Details, choose Select template (for example New catalog file) and Send in specific language (leave Each recipient's language).

   

   Recipients and template.
4. Template Tokens lists the tokens of the template. Give each one a value: type it, or press the tag button next to a token and pick a value (Project, Initiator, Recipient, Email Signatures, Email Footers). Until each has a value, a yellow box lists what is Still missing.

   

   Every token has a value.
5. Under Advanced settings, Send email on behalf of sets who speaks in the message; Select email provider is set to the project default (Test Me (Fake) here). Then fill the trigger's own fields and press Save:

   Field	Required	What it does	Example
   Order	no	Run order when several triggers listen to one event; lower runs first.	1
   Name the trigger	yes	The name in the list.	Tell the catalog team
   Description	no	Free text.	Emails the catalog team when a file lands in catalog/.
   Is this trigger enabled?	no	On: the trigger runs. Off: saved but quiet.	on

   

   The trigger's own fields.

A new trigger starts enabled. Today the Is this trigger enabled? switch is still drawn in the off position on a new trigger; that is a display fault — the trigger is saved enabled (the list shows Enabled: Yes). Disable it from the Actions menu if it should not run yet.

Result

Cloud goes back to File Triggers with the new row (When uploaded, Send Email, Enabled: Yes). The next matching file runs it: in the example, uploading catalog/summer-2026-catalog.pdf produced an email campaign with status Completed through Test Me, visible in Email → Campaigns. A file uploaded into mugs does not fire it.

The new trigger in the list.

The email the trigger sent, in Email → Campaigns.

A run that cannot send (template misses a project language, provider off) marks the trigger Needs attention.

Change or remove it later

• Edit — Edit a trigger.

• Disable / Enable — Enable or disable a trigger.

• Delete — Delete a trigger.

Do it from code

const { id } = await norbix.hub.files.saveFilesTrigger({
  trigger: {
    type: 'Files',
    when: 'OnFileUploaded',
    folder: 'catalog/2026',
    name: 'Tell sales about 2026 catalogs',
    isEnabled: true,
    action: {
      type: 'email',
      templateId: 'tmpl_73E0M90SdGHBZtZM1Y3E1k', // New catalog file
      integrationId: 'int_6OFbF0V9iR8sGMKr2loYAU', // the email provider (Test Me)
      deliverySettings: {
        recipientsSourceType: 'Email',
        recipients: ['[e-mail]'],
        mappedTokens: [
          { key: 'Recipient.FirstName', value: 'Sales team', resolver: 'Custom' },
          { key: 'Email.SignatureId', value: 'emlsgn_62lhoSNxPmBjR7KoUNfE8n', resolver: 'Custom' },
          { key: 'Email.FooterId', value: 'emlftr_6hU4LyFZt7kY9WANxED3UQ', resolver: 'Custom' },
          { key: 'Project.Name', value: 'Project.Name', resolver: 'Project' },
          { key: 'Project.Url', value: 'https://acme.example', resolver: 'Custom' },
        ],
      },
    },
  },
});
console.log(id); // trg_1p50DsItoELswoqBLXU157

norbix hub files trigger save --trigger:json '{"type":"Files","when":"OnFileDeleted","name":"Temp (cli)","isEnabled":true,"action":{"type":"email","templateId":"tmpl_73E0M90SdGHBZtZM1Y3E1k","integrationId":"int_6OFbF0V9iR8sGMKr2loYAU","deliverySettings":{"recipientsSourceType":"Email","recipients":["[e-mail]"]}}}'

The SDK reference has one example per action. The client setup is on the Files page. API: Save Files Trigger