Stalled Deal form intake with CRM creation and owner notification

How it works

1. 1.The Form Webhook node accepts POST requests at path sales-stalled-deal-monitor-form using responseNode mode.
2. 2.The Normalize Form Set node maps body into input and tags source as Stalled Deal Monitor.
3. 3.The Required Fields IF node routes non-empty input to the creation branch and empty input to the missing-fields branch.
4. 4.Create CRM Record sends a POST with a placeholder body to the example CRM API using generic credentials.
5. 5.Notify Owner sends a similar POST to the notify API, then Respond OK returns status created.
6. 6.Respond Missing returns status missing-fields for empty input.

Use cases

• Capturing stalled-deal review submissions from an external form into a CRM system.
• Notifying the deal owner immediately after a valid submission and confirming receipt to the sender.

Requirements

• Configure genericCredentialType credentials for both HTTP Request nodes and replace the api.example.com placeholder URLs and body values with real endpoints and fields.
• Activate the workflow in n8n so the webhook can receive requests, and extend the Set/IF nodes to validate the actual required form fields.

Setup and testing in n8n

1. POST to the webhook path with a non-empty body and verify both HTTP nodes run and the response is created.
2. POST with an empty body and verify the response is missing-fields from Respond Missing.
3. Inspect the n8n execution log to confirm the node connection flow.

Service Value

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