Webhook Intake Router with Validation and Forwarding

How it works

1. 1.Webhook Trigger receives POST requests at path content-social-content-idea-intake-router-intake with responseMode set to respond via a Respond to Webhook node.
2. 2.Normalize Input copies the request body into an input field and adds a fixed source value naming the template.
3. 3.Validate Input checks that the input field is not empty.
4. 4.Non-empty input goes to Forward To Service, which sends a POST with a placeholder body parameter to api.example.com using genericCredentialType authentication.
5. 5.Respond Success returns {"status":"accepted"} after forwarding, while Respond Invalid returns {"status":"invalid"} for empty payloads.

Use cases

• Template starting point for routing content idea submissions to an internal API endpoint.
• Gating intake so empty payloads never reach the downstream service.
• Returning synchronous JSON status responses to the calling client.

Requirements

• An n8n instance with the workflow activated to accept live webhook traffic, since it is inactive by default.
• A generic HTTP credential configured and selected on the Forward To Service node for genericCredentialType authentication.
• Replacement of the placeholder URL and the placeholder body parameter with real endpoint and payload values.

Setup and testing in n8n

1. Run the workflow in test mode from the n8n editor and send a POST with a JSON body to the displayed test webhook URL.
2. Verify that a non-empty body produces an accepted response after the HTTP request node executes.
3. Send a request with an empty body and confirm an invalid response is returned without forwarding.

Service Value

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