Appdor Enquiry Form to Email Alerts via n8n Workflow Automation

Appdor enquiry forms to automated email alerts—with duplicate-safe n8n routing

This n8n workflow captures new and returning enquiries via an n8n Form, checks for duplicates in your Appdor database, preserves existing status, and sends the right email notifications to your fixed Sales/Support/Billing inboxes (or an escalation inbox for urgent requests). It also stops safely when lookups, saving, or email delivery fail—so you don’t create messy records or notify the wrong team.

What this workflow does

• Collects enquiry details (Name, Email, Message, Enquiry type, Priority) through an n8n Form with required value validation, length limits, and configured category/priority enforcement (Sales, Support, Billing; Normal or Urgent).
• Normalizes and de-duplicates the submitted email (trimmed, case-insensitive) and queries Appdor for up to two matches.
• Handles match outcomes safely:
  • Zero matches: creates a new enquiry.
  • One match: updates the latest enquiry using the returned record version and preserves existing Status.
  • Two matches: stops for human duplicate review.
• Confirms the saved record ID before notifying teams.
• Routes notifications by priority:
  • Normal → fixed Sales/Support/Billing inbox
  • Urgent → fixed escalation inbox
• Sends notification emails with routing metadata including the record ID, while excluding submitted names, email addresses, and message content.

Use cases

• Automate enquiry handling for a SaaS landing page using n8n Form inputs.
• Prevent duplicate Appdor records with case-insensitive email matching and a “two matches” human review stop.
• Escalate high-priority enquiries to a dedicated inbox while keeping normal enquiries routed to the correct team.

Technical details

• Nodes / approach: form trigger, HTTP request, code (validation/normalization/duplicate logic), email send, and a sticky note for workflow clarity.
• Includes separate Stop And Error branches for lookup, save, and SMTP failures.
• Automatic retries are disabled; notification is retried only after an SMTP failure, and the form confirms success only after successful notification.