Failed login form webhook with CRM and owner notification

How it works

1. 1.The Form Webhook node accepts POST requests at path it-ops-security-failed-login-monitor-form with responseMode=responseNode.
2. 2.Normalize Form sets source to a fixed string and input to the request body.
3. 3.Required Fields checks that input is not empty and routes to the success or failure branch.
4. 4.Success branch: Create CRM Record sends a POST with generic credentials, Notify Owner sends a notification POST, and Respond OK returns {"status":"created"}.
5. 5.Failure branch: Respond Missing returns {"status":"missing-fields"}.

Use cases

• Logging failed-login security reports submitted via a web form into a CRM system.
• Notifying a security owner or on-call responder about each submitted report.
• Automatically rejecting incomplete form submissions with an immediate JSON response.

Requirements

• The workflow must be activated for the webhook to receive requests.
• HTTP generic credentials must be configured for both Create CRM Record and Notify Owner nodes.
• Placeholder URLs and REPLACE_WITH_YOUR_VALUE body values must be replaced with real endpoints and identifiers.
• Callers must submit a non-empty input field in the request body.

Setup and testing in n8n

1. POST to /webhook/it-ops-security-failed-login-monitor-form with a non-empty body and verify the {"status":"created"} response.
2. Send an empty body and verify the {"status":"missing-fields"} response.
3. Inspect the execution log to confirm the correct branch and HTTP nodes ran.

Service Value

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