# Data table - Workflow trigger | Docs - nodulz

Source: https://nodulz.com/docs/nodes/workflow_table_trigger

Language: en

Starts the workflow when an internal table in this workflow is modified

## Usage and specifics

The table belongs to the current workflow. triggerOnOwnRun controls events from its own runs; check this setting to avoid an unintended chain of triggers.

Technical type : `workflow_table_trigger`. Runtime : `nodulz`.

## Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the [credentials guide](/docs/credentials) if a remote source or execution target requires access.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `tableScope` | `enum` | `"workspace"` | `workspace`, `legacy` |
| `tableId` | `string` | - | - |
| `table` | `string` | `""` | - |
| `events` | `array` | `["create_table","alter_table","drop_table","clear_table","insert","bulk_insert","update","delete"]` | - |
| `triggerOnOwnRun` | `boolean` | `false` | - |
| `testPayload` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `triggerOnOwnRun`<br>Trigger during the same run | Off by default: avoids loops when this workflow writes via the Data table node. |
| `testPayload`<br>Test payload | Used when manually testing the trigger in the editor. |

## Examples

- Output includes event, table, row or rows, and rowCount depending on the operation.

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "tableScope": "workspace",
  "table": "",
  "events": [
    "create_table",
    "alter_table",
    "drop_table",
    "clear_table",
    "insert",
    "bulk_insert",
    "update",
    "delete"
  ],
  "triggerOnOwnRun": false,
  "testPayload": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)