Overview
This node triggers workflows based on changes detected in a Samba (SMB2) filesystem. It monitors specific files, folders, or entire drives for events such as file creation, deletion, updates, and folder modifications. This is useful for automating processes that depend on file system changes, such as syncing files, processing new uploads, or auditing file activity.
Practical examples:
- Trigger a workflow when a new file is created in a shared folder to automatically process or move the file.
- Monitor a specific configuration file for updates and trigger a deployment workflow.
- Watch an entire drive for any folder creation to log or notify administrators.
Properties
| Name | Meaning |
|---|---|
| Trigger On | Selects what to monitor: currently only "Changes Involving a Specific Folder" is available. |
| Recursive | Boolean option to watch subfolders recursively within the specified folder. |
| Folder | The path of the folder to watch for changes. Only applicable when "Trigger On" is set to "specificFolder". |
| Watch For | Specifies which event to trigger on within the watched folder. Options include: - File Created - File Deleted - File Updated - Folder Created - Folder Deleted - Folder Updated - Watch Folder Updated |
| Changes within subfolders won't trigger this node | Notice informing users that changes inside subfolders do not trigger the node unless recursive watching is enabled. |
Note: Other properties related to watching a specific file or any file/folder on a drive are defined but not active under the selected resource/operation.
Output
The node outputs JSON data representing the detected change event. Each output item contains a json field with details about the change, including:
changeType: Numeric code indicating the type of change.- Additional metadata about the changed file or folder (e.g., name, path, timestamps).
Binary data is not produced by this node; it strictly reports filesystem event information.
Dependencies
- Requires connection credentials to access the SMB2 server (an API key or authentication token).
- Uses an internal helper module to connect and watch directories on the SMB2 share.
- No additional external services are required beyond the SMB2 server itself.
Troubleshooting
- Connection errors: If the node fails to connect to the SMB server, ensure the provided credentials and network access are correct. The error message will indicate failure to connect and provide a readable error description.
- No triggers firing: Verify that the correct folder path and event type are selected. Also, check if recursive watching is needed for subfolder changes.
- Unsupported events: Some event types may not be supported depending on the SMB server capabilities.
- Permission issues: Ensure the SMB user has sufficient permissions to watch the specified folder.
Links and References
- Samba (SMB) Protocol Overview
- n8n Documentation - Creating Custom Nodes
- Node.js Debugging Utility (used internally for debug logs)