Post-resolution checklist input validation and forwarding

How it works

1. 1.Webhook listens for POST requests on the configured path and defers the response to a response node.
2. 2.A Set node maps the request body to an input field and adds a source label of Post-Resolution Checklist.
3. 3.An IF node routes items based on whether input is non-empty.
4. 4.An HTTP Request node POSTs to api.example.com using generic credentials with a placeholder body value that must be replaced.
5. 5.A Respond to Webhook node returns accepted after forwarding, or invalid when input is empty.

Use cases

• Front-door validation gate for post-resolution checklist submissions before sending them to an external system.
• Filtering empty or malformed support form payloads at intake.

Requirements

• Activate the workflow and replace the placeholder URL and body parameter with real values.
• Configure Generic Credentials for the HTTP Request node and ensure the webhook path is unique.
• Store the webhook URL securely since anyone with it can submit requests.

Setup and testing in n8n

1. Send a POST request with a non-empty body and expect an accepted response plus a call to the forwarding endpoint.
2. Send a POST request with an empty body and expect an invalid response with no outbound call.

Service Value

Ready-made workflow template for automation delivery and service execution.