> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sndbox.app/llms.txt
> Use this file to discover all available pages before exploring further.

# File Watch Trigger

> Watch an approved folder. Exact configuration, ports, placement, and execution behavior.

**Node type:** `file_watch_trigger` · **Version:** `1` · **Category:** Triggers

Watch an approved folder. This node does not declare an external side effect.

## Configuration

| Field     | Type   | Default       | What it controls                                                                                   |
| --------- | ------ | ------------- | -------------------------------------------------------------------------------------------------- |
| `folder`  | path   | `""`          | Folder selected through the operating-system picker and added to the workflow permission boundary. |
| `events`  | array  | `["created"]` | File-system event types that can start the workflow. Values: `created`, `modified`, `deleted`.     |
| `pattern` | string | `""`          | Optional glob used to filter names inside the approved folder.                                     |

## Workflow JSON

The editor stores this node with the following implemented default configuration:

```json title="Default node configuration" theme={"system"}
{
  "type": "file_watch_trigger",
  "version": 1,
  "configuration": {
    "folder": "",
    "events": [
      "created"
    ],
    "pattern": ""
  }
}
```

Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See [Variables and data mapping](/workflows/variables-and-data).

## Inputs

This node has no typed ports in this direction.

## Outputs

| Port    | Type     | Required | Description |
| ------- | -------- | -------- | ----------- |
| `event` | `object` | No       | File event  |

## Where it can run

* Desktop local runner
* Paired self-hosted runner
* Hosted runner

## Test and inspect

Use **Test node** in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.