Patient duplicate-record sweep form intake with CRM creation

How it works

1. 1.A webhook node accepts POST requests on path healthcare-admin-duplicate-patient-record-sweep-form and defers the response to a respond node.
2. 2.A Set node reshapes the payload into source and input fields taken from the request body.
3. 3.An If node routes non-empty input to the CRM creation path and empty input to a missing-fields response.
4. 4.The first HTTP Request node posts to a CRM create endpoint using generic credentials, followed by a notify-owner HTTP call.
5. 5.RespondToWebhook nodes return {"status":"created"} on success or {"status":"missing-fields"} on validation failure.

Use cases

• Capturing healthcare admin submissions for a duplicate patient record sweep initiative.
• Logging each submission as a CRM record and alerting the responsible owner in downstream systems.

Requirements

• Configure Generic Credential Type authentication for both HTTP Request nodes and replace the api.example.com placeholder URLs and REPLACE_WITH_YOUR_VALUE body values with real endpoints.
• Activate the workflow so the webhook path is reachable, and ensure callers POST a non-empty body.

Setup and testing in n8n

1. POST a payload with a populated body to the webhook path and verify the {"status":"created"} response after replacing placeholder URLs.
2. POST an empty body and verify the {"status":"missing-fields"} response.
3. Inspect the n8n execution log to confirm both HTTP nodes ran on the success branch once real endpoints are configured.

Service Value

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