Describe the manual process first
Record who receives an enquiry, where the contact is stored and what happens next. Automation should support the required process, not send every available field to every tool. In a simple example, a form supplies name, email, service and message; the CRM creates an enquiry and the responsible person receives a notification.
Agree rules before connecting tools
Define required fields, service mapping and duplicate handling. The same email address does not always mean the same project. For example, retain the contact but create a separate enquiry for a new requirement. Decide who needs access, which systems are necessary and what information belongs in the notification.
Plan failure and retries
A CRM can be unavailable, a token can expire or a connection can fail. Decide when to retry and how to avoid duplicate records. Error notifications should not expose full enquiry content to people who do not need it. One successful run is not enough: also test invalid input and an unavailable destination.
Use AI for a defined task
If AI categorises enquiries, define the categories and cases needing human review. Do not let it automatically promise prices or terms to customers. Check what data reaches the model provider and whether it is needed. An n8n and AI integration should reflect the business’s actual tools, permissions and working process.
Handle failures without losing enquiries
Assign a durable submission ID in the receiving system before writing to the CRM. Distinguish validation failures, permission errors and temporary API outages. Retry only operations that are safe to repeat and respect provider retry timing for rate limits. After retries are exhausted, retain a pending state and alert the process owner without distributing the full enquiry.
A submission ID is not an email address
The same customer can send two different enquiries. Do not discard one just because the email repeats. Use the individual submission ID with an atomic write or uniqueness constraint to make retries safe. Check the previous operation’s outcome before creating another record, particularly after an API timeout.
Acceptance test scenarios
Test a valid enquiry, missing required data, duplicate delivery of one webhook, a timeout after record creation, API rate limits, revoked access and manual recovery. Expect one record per submission and a clear status history. Limit permissions to the required actions and keep test records separate from real customers.