Stale dataset report form with CRM creation and owner notification

How it works

1. 1.A webhook node listens for POST requests on path data-engineering-stale-dataset-monitor-form with the response deferred to a respond node.
2. 2.A Set node adds source ("Stale Dataset Monitor") and copies the request body into an input field.
3. 3.An If node routes execution based on whether input is not empty.
4. 4.On the true branch, Create CRM Record and then Notify Owner each send authenticated POST requests with a placeholder body parameter.
5. 5.Respond OK returns {"status": "created"} after notification; the false branch returns {"status": "missing-fields"}.

Use cases

• Capturing stale-dataset reports from an external form and recording them in a CRM.
• Notifying a dataset owner whenever a new stale-dataset report is submitted.

Requirements

• Activate the workflow and replace the api.example.com URLs and REPLACE_WITH_YOUR_VALUE placeholders with real endpoints and payloads.
• Configure Generic HTTP credentials for the Create CRM Record and Notify Owner request nodes.
• Network access from the n8n instance to the CRM and notification services.

Setup and testing in n8n

1. POST to the configured webhook path with a non-empty body and verify the {"status": "created"} response.
2. POST with an empty body and verify the {"status": "missing-fields"} response and that the HTTP nodes were skipped.
3. Inspect an execution log to confirm node ordering and the source/input field values.

Service Value

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