Validate a single node configuration without saving it. Useful for pre-flight checks when building a flow programmatically. Send the same node object shape you would put inside a flow version (see the flow-node schema).
Required fields: id, type, before, after. The before and after edge arrays MUST be present even when empty ([]) — omitting them currently causes a server error instead of a validation error.
id must be an integer, not a string. Node config lives in the payload object, with automation set to the string "auto".
A valid node returns 204 No Content (empty body).
Node type. See the table above for allowed values.
Incoming edges (empty for entry nodes). Required, may be [].
Outgoing edges (empty for the end node). Required, may be [].
{ "template": "Hi {{first_name}}, happy to connect!", "fallback_send": true, "template_uuid": null }
Node configuration. Object whose shape depends on type (see table), or [] for nodes with no configuration.
Delay before this node runs, relative to the previous step (e.g. 7200 = 2h, 86400 = 1 day). 0 = run immediately.
Required when saving a node via createFlowVersion (an ISO-8601 timestamp; use the current time for new nodes). Not required by validate-node.
- object
- Array of any
curl -i -X POST \
https://leadgen.grinfi.io/flows/api/flow-versions/validate-node \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"id": 1,
"before": [],
"after": [],
"type": "linkedin_send_connection_request",
"automation": "auto",
"payload": {
"template": "Hi {{first_name}}, happy to connect!",
"fallback_send": true,
"template_uuid": null
},
"delay_in_seconds": 0
}'