Creating File Triggers

A file trigger initiates a new task whenever a file is created, modified, or deleted in a specified location.

Files can reside in two folder options:

  1. File Systems: local and network folders

  2. Sharepoint (on-premises version) folder

To create a file trigger:

Each robot that could have a task assigned to based on this trigger must have connectivity and access rights to the specified root folder (so that it can read and act on the folders/files within it)

The Nintex RPA Server must also have access to this folder (to monitor it)

Take special care with Microsoft Office files

Microsoft Office creates temporary files when documents are opened. As a result, editing Office files directly within the monitored folder may cause unexpected results (e.g., the trigger may initiate multiple tasks for a single file modification).

Renaming files

When you set the File trigger to monitor renamed file events, keep in mind that the trigger monitors the new name of the file, not the change in the old name.

For example: Say you have set the trigger to monitor the file name 1.2*.exe and ticked the New (or renamed) file check box. If you change the file to, say, John.exe, the event will not be identified as a renamed file. However, if you have a file called John.exe and you change the name to 1.2x.exe, the renamed file is identified as renamed.