Workflow event

Node catalog Triggers
On this page

Receives a call from another nodulz workflow (Call workflow action)

Usage and specifics

This entry point receives Call Workflow requests. Publish the target workflow and use its trigger identifier.

Technical type : workflow_event. 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 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
testPayload string "" -

Configuration help

testPayload
Test payload
JSON injected as payload when manually testing this trigger. Example: JSON object - downstream use {{ nodes..payload }}.

Examples

  • Example: JSON object - downstream use {{ nodes..payload }}.
  • Copy this id into the caller workflow or pick it from the Call workflow node list.

Initial configuration

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

json
{
  "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, Executions, Node catalog.