1. Executive Summary ​Automation workflow designed to capture incoming contact form submissions, sanitize contact data, and trigger real-time notifications to a Discord channel for immediate sales team visibility. ​2. Technical Architecture ​Webhook: Receives incoming POST requests from the website form. ​Format Phone: Normalizes phone numbers by stripping non-numeric characters. ​Discord Notify: Sends the processed lead information to a specified Discord channel. ​Mermaid Flowchart: graph LR A[Webhook] --> B[Format Phone] B --> C[Discord Notify] C -. Failure .- D[Error Trigger] Modularization Proposal: ​The Format Phone node should be converted into a reusable Sub-workflow (e.g., SF_Normalize_Contact_Data), as phone number sanitation is required across multiple lead-generation workflows. ​3. Data Mapping Specification ​[phone] -> [phone_clean] ​Transformation: Regex-based removal of non-digit characters (\D). ​Type: String. ​Note: Essential for standardizing format for CRM compatibility. ​4. Configuration & Prerequisites ​Environment Variables: DISCORD_WEBHOOK_URL. ​Credentials: Discord Webhook URL (stored securely). ​5. Security & Compliance ​Authentication: CRITICAL ALERT: Discord Webhook URL containing a secret token is hardcoded in the Discord Notify node. Remediation: Store this URL as an environment variable or n8n Credential object to prevent exposure in version control. ​Data Protection: Ensure PII (Personal Identifiable Information) such as full names or addresses are not logged in the Discord message body if the channel is accessible to unauthorized personnel. ​Best Practices: Always use environment variables for third-party service endpoints. ​6. Retry Logic & Error Handling ​Strategy: Configure the Discord Notify node with a 3-retry attempt policy using an exponential backoff. ​Graceful Degradation: If Discord is unavailable, route the payload to an "Error Queue" (Database) to attempt re-delivery once connectivity is restored. ​Alerting: Configure an Error Trigger to log execution failures in a Google Sheet or database for audit purposes. ​7. Maintenance Guidelines ​Tokens: Conduct a quarterly audit of webhook URLs to ensure integration security. ​Performance: Periodically purge the workflow execution history to maintain performance in the n8n database.