DocumentationWorkflowsTriggers
Nextcloud · New/changed file node
Kicks off the workflow as soon as a file is added or changed in a watched Nextcloud folder. Anymize waits a short grace period so the upload is finished before the workflow fires. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Kicks off the workflow as soon as a file is added or changed in a watched Nextcloud folder. Anymize waits a short grace period so the upload is finished before the workflow fires.
Use Nextcloud · New/changed file as a clearly defined step in an anymize workflow.
- Starts a new workflow run.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Nextcloud · New/changed file from the node catalog.
- 02Select your nextcloud connection. You can create it directly in the workflow if needed.
- 03Complete the required fields and map values from previous steps.
- 04Run the node with a small test record and inspect its output.
- 05Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Nextcloud · New/changed file has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Folder | Which folder to watch (e.g. /Invoices). Default: root. | Standard |
| Name contains (optional) | Only trigger on files whose name contains this text. | Standard |
| File extension (optional) | Only trigger on files with this extension (e.g. pdf, csv). | Standard |
| Check interval (seconds) | How often Anymize checks the folder for new files. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | This trigger does not require an input. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Path | File path relative to the Nextcloud root. | text |
| File name | Configure this value in the node panel. | text |
| Folder | Configure this value in the node panel. | text |
| Size (bytes) | Configure this value in the node panel. | number |
| MIME type | Configure this value in the node panel. | text |
| Modified at | Configure this value in the node panel. | text |
| File ID | Configure this value in the node panel. | text |
Example and test run
Example file event: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"path": "/Rechnungen/2026-04-rechnung.pdf",
"name": "2026-04-rechnung.pdf",
"folder": "/Rechnungen",
"size": 84213,
"mime": "application/pdf",
"lastModified": "2026-04-18T09:00:00Z",
"fileId": "00123456"
}Access and security
This node uses a connected nextcloud account. Review the requested permissions and grant only the required access.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- Connection rejected: reconnect the service and grant the permissions required by this step.
- Workflow does not start: activate it and check the trigger's test and production mode.