MongoDB

Node catalog Triggers

On this page

Starts the workflow when a MongoDB collection changes (change stream)

Usage and specifics

Change streams require a replica set or a compatible cluster. A standalone MongoDB instance is insufficient. Select a collection and events before publishing.

Technical type : mongodb_trigger. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : mongodb

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

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
`credentialId`	`string`	`""`	-
`collection`	`string`	`""`	-
`events`	`array`	`["insert"]`	-
`testPayload`	`string`	`""`	-

Configuration help

credentialId MongoDB credential: Choose a saved MongoDB credential.
collection Collection: Name of the collection to use.
events Events: Choose the changes that start the workflow.

Initial configuration

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

json

{
  "credentialId": "",
  "collection": "",
  "events": [
    "insert"
  ],
  "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.