Hi,
It wasn’t specifically mentioned in the documentation, but just wanted to confirm that calling a custom node does not count toward the payload limit; true?
Feels like it falls into the same category as calling a workflow from another workflow using the workflow trigger node.
Thanks,
Stephen
Correct, invoking a custom node does not in itself count as a billable payload. It doesn’t even show up as a separate, non-billable payload when using the API to retrieve those extended stats. It’s just an extension of the current workflow run.
There are, of course, things that you could do within the execution of that custom node that would count as a billable payload, though - publishing a message using an MQTT Node or reporting state through a Device: State Node for example.