Are you actually ready to do this yourself?

• [ ] A named office or service manager owns the process.
• [ ] A second person can disable it and operate the fallback.
• [ ] You can identify the authoritative customer, job and appointment records.
• [ ] You can describe exceptions without relying on the owner’s memory.
• [ ] You have permission to use the required integrations.
• [ ] Someone will review errors, costs and customer complaints.
• [ ] You can obtain competent privacy and technical-safety advice where needed.
• [ ] There is an operational benefit worth measuring—not simply enthusiasm for AI.

If ownership, records or fallback cover are missing, fix those first. A paid subscription should not become the substitute for deciding who returns calls or approves bookings.

For workflow tooling, distinguish configuring a hosted service from operating infrastructure. n8n’s documentation separates managed cloud deployment from self-hosting, where deployment, configuration, security and maintenance remain part of the work. Our recommendation is to avoid self-hosting your first customer-facing workflow unless your IT team already supports that kind of service. (github.com)