Booking form to CRM, invoice and Slack in one workflow (n8n)

01Summary

1. A booking form feeds one n8n workflow (14 nodes) that validates, prices, finds or creates the CRM contact and raises the invoice.
2. In the test run 12 of 14 bookings went through end to end and 2 were rejected with a reason.
3. 4,089.80 was invoiced across 7 contacts, with a Slack message for each booking.

In the test run 12 of 14 bookings went through end to end and 2 were rejected with a reason.

Key point, computed from the sample files

02The scenario

In this scenario every booking is handled three times by hand: once in the inbox, once in the CRM and once in the invoicing tool. Pricing mistakes and missed messages are the usual result.

03Issues in the data

04How I approached it

• A webhook that receives the booking form and a code step that validates and prices it from a rate card.
• Find-or-create logic for the CRM contact, so returning customers are not duplicated.
• Invoice creation and a Slack message with the key details; a review alert for rejected submissions.
• An n8n export with 14 nodes, tested against local stand-ins for the CRM, invoicing and Slack.

05How this applies to your business

1. Assess and designMap the current process, size the gaps from your own data, agree the design and a written scope.
2. Build and testBuild in your own tools with the checks built in, then run real cases end to end.
3. Document and hand overSOPs, a walkthrough and a handover, so your team runs it without me.

06Controls and checks

07What the files show

• 12 accepted submissions created 12 unique invoices for 7 contacts (returning customers matched).
• 2 submissions were rejected with a clear reason (bad email, service not on the rate card).
• The run log in the download shows every request and response.

08Risks and how the build handles them

09Appendix: files

A. Screenshots of the deliverable

booking-crm-invoice-slack.n8n.json

Exhibit 8: Workflow diagram: form webhook, validate and price, find or create CRM contact, create invoice, Slack message, review alert

Source: sample files

invoice.html

Exhibit 9: Invoice record created by the workflow, rendered from the invoice data

Source: sample files

Slack · #bookings

Exhibit 10: Slack message posted for a new booking with contact, invoice number and total

Source: sample files

const errors = [];
const email = String(b.email || '').trim().toLowerCase();
if (!/^[^@\s]+@[^@\s]+\.[a-z]{2,}$/.test(email)) errors.push('A valid email address is required');
const titleCase = s => String(s || '').trim().toLowerCase().replace(/\b[a-z]/g, c => c.toUpperCase());
const name = titleCase(b.name);
if (!name) errors.push('Name is required');

B. Downloadable files

Sample build: realistic data, built to show how I'd handle this work. Names are placeholders and no client data is used.