DEV Community: Softomate solutions

Building a client onboarding automation for a UK professional services firm: n8n workflow walkthrough with HubSpot, DocuSign, and Google Drive

Softomate solutions — Mon, 08 Jun 2026 13:18:33 +0000

This is a full technical walkthrough of the client onboarding automation we built for a London financial consultancy. The workflow saves 22 hours per week and runs completely without human input once a deal is won in HubSpot.

TRIGGER: DEAL MOVED TO WON IN HUBSPOT

The workflow triggers on the HubSpot Deal Stage Changed webhook. In HubSpot, go to Settings, Integrations, Private Apps, create a new private app with these scopes: crm.objects.deals.read, crm.objects.contacts.read, crm.objects.companies.read. Copy the access token.

In n8n, add a HubSpot Trigger node. Set it to Deal Stage Changed. Add a Filter node after it: only continue if dealstage equals closedwon.

DATA COLLECTION STEP

Add a HubSpot node in Get mode. Get the Deal by ID using the deal ID from the trigger payload. Then get the associated Contact using the associations.contacts.results[0].id from the deal response. Then get the associated Company.

You now have all the data needed for the rest of the workflow: client name, company name, email, deal value, service type, start date.

STEP 1: GENERATE THE PROPOSAL PDF

Add an HTTP Request node. POST to your PDF generation API (we use PDFMonkey but pdf.co and DocRaptor work similarly). In the body, map the fields from the HubSpot data to your template variables. The response includes a download URL for the generated PDF.

STEP 2: SEND DOCUSIGN ENVELOPE

Add an HTTP Request node. POST to the DocuSign eSignature API endpoint. In the envelope definition, embed the PDF URL from step 1. Set the signer email and name from the HubSpot contact data. Set the signing tab positions to match your contract signature fields. DocuSign returns an envelopeId in the response. Store this using the Set node for later reference.

STEP 3: CREATE GOOGLE DRIVE FOLDER STRUCTURE

Add a Google Drive node. Create a folder named after the company under your Clients parent folder. Then create seven subfolders inside it: Contracts, Proposals, Onboarding, Meeting Notes, Deliverables, Invoices, Correspondence.

Map the main folder ID from the Google Drive response to a Set node field. You will use this URL in the HubSpot note later.

STEP 4: SEND CALENDLY INVITATION

Use Calendly API to create a one-off event type for the onboarding call. POST to the Calendly single-use scheduling link endpoint with the client email pre-filled. Send the scheduling URL to the client via HubSpot Engagement API as a task with a note.

STEP 5: CREATE XERO INVOICE

Add an HTTP Request node. POST to the Xero Invoices API. Map deal value to InvoiceAmount. Set DueDate to 30 days from today using n8n date expression. Set ContactID to the Xero contact matching the company (requires a pre-lookup step using the Xero Contacts GET endpoint filtered by company name).

STEP 6: UPDATE HUBSPOT WITH ALL REFERENCES

Create a HubSpot note on the deal with: Google Drive folder link, DocuSign envelope ID, Calendly scheduling link, Xero invoice number. Set deal property Onboarding Status to In Progress.

ERROR HANDLING

Add an Error Trigger workflow. If any step in the main workflow fails, post a Slack message to a dedicated channel with: company name, step that failed, error message, deal URL. This gives a human a five-minute window to intervene before the client notices anything went wrong.

Full business process automation service: softomatesolutions.com/business-process-automation-london/

Setting up GoHighLevel for UK agencies: the complete technical guide including GDPR, DNS, and snapshot architecture

Softomate solutions — Mon, 08 Jun 2026 13:11:22 +0000

GoHighLevel is built for the US market. The documentation assumes US email laws, US timezones, and US data processing. UK agencies setting it up for the first time hit the same five blockers every single time. This guide covers all of them plus the snapshot architecture that makes GHL scalable for an agency serving multiple clients.

BLOCKER 1: EMAIL AUTHENTICATION

GHL uses Mailgun for email delivery. Without proper DNS authentication, all marketing emails go to spam.

Go to Settings, then Email Services, then click Add Sending Domain. Enter your domain. GHL shows you three DNS records to add: one SPF TXT record, one DKIM TXT record, one DKIM CNAME record. Add all three to your domain DNS provider. Verify in GHL. This takes 15 minutes and DNS propagation can take up to 24 hours.

Also set a dedicated sending subdomain like mail.yourdomain.com rather than sending from your root domain. This protects your root domain sender reputation if any campaign generates spam complaints.

BLOCKER 2: GDPR CONSENT ON FORMS

Default GHL forms have no consent checkboxes. UK ICO regulations require explicit opt-in consent before sending marketing emails. The implementation:

Add a checkbox field to every form with this label: I agree to receive marketing communications from [Company Name]. I can unsubscribe at any time.

In the field settings, mark it as required. Create a custom field called Marketing Consent with type Yes or No. Map the checkbox to this field. Create a workflow trigger: When Marketing Consent equals Yes, add tag Marketing Approved. Use the Marketing Approved tag as a required filter on every email campaign broadcast.

This gives you a defensible audit trail if the ICO ever asks.

BLOCKER 3: TIMEZONE CONFIGURATION

Fix timezone in two places. First: Settings, Business Info, set timezone to Europe/London. Second: open each calendar in Calendars, Settings. Check the timezone field on each calendar separately. GHL sometimes retains a separate timezone on individual calendars that overrides the account setting.

BLOCKER 4: DEMO DATA CLEANUP

Before building any workflows, go to Contacts and delete all sample contacts. Then go to Conversations and clear sample conversations. Run a test workflow with a real test contact to verify the sample data is fully removed before any live campaign runs.

BLOCKER 5: SNAPSHOT ARCHITECTURE

If you are an agency managing multiple client sub-accounts, build everything in a dedicated master template sub-account first. Never build workflows, pipelines, funnels, or email sequences directly in client sub-accounts before the template is finalised.

To create a snapshot: Settings, Snapshots, Create Snapshot, select everything you want to copy. To apply to a new client: when creating the sub-account, select the snapshot. The entire setup copies automatically.

Snapshots do not copy contacts, campaigns already sent, or sub-account-specific integrations like Stripe or payment connections. These need to be configured per client.

Full UK agency guide: softomatesolutions.com/blog/best-gohighlevel-agencies-london-2026/

n8n vs Make.com vs Zapier in 2026: what we learned migrating eight UK businesses, with real cost data

Softomate solutions — Mon, 08 Jun 2026 13:00:14 +0000

This is not a generic comparison. Every number here comes from actual migrations we completed between January and May 2026. Eight businesses. Three platforms. Real outcomes.

WHY BUSINESSES LEFT ZAPIER

Multi-step automations at real volume cost 149 to 382 pounds per month on Zapier. A typical UK SME running CRM sync, email triggers, Slack notifications, and form processing consumes 10,000 to 20,000 tasks per month. At that volume the Zapier bill is hard to justify when alternatives exist.

MIGRATIONS 1 TO 3: N8N SELF-HOSTED

All three had technical people on the team. Previous Zapier cost: average 298 pounds per month. New n8n cost: 8 pounds per month for Hetzner CX22 VPS. Licence is free when self-hosted.

Migration took three to four weeks per business. Longer than expected. Main issues:

Zapier delay nodes do not map directly to n8n Wait nodes. Timing on follow-up email sequences needed manual recalibration.

Zapier Formatter tool has no n8n equivalent. Replicate it with the Code node and simple JavaScript.

n8n does not alert on workflow failure by default. Build an Error Trigger workflow that posts to a Slack channel. Without this you discover failures days after they happen.

Budget two to three times your initial migration estimate. All three businesses are still on n8n six months later.

MIGRATIONS 4 TO 7: MAKE.COM

Four businesses. All non-technical teams. Decided by: visual interface similar to Zapier, pricing, EU data hosting.

Make operations model is more efficient than Zapier tasks. A branching workflow that needed three Zaps becomes one scenario. Pricing at 10,000 operations: 16 pounds versus Zapier 149 pounds.

Migration was one to two weeks per business. The issue is operation counting. A scenario with many modules can consume eight or more operations per run. New users underestimate monthly usage by a factor of three. Start with a higher plan and scale down after you see actual usage.

Make EU data hosting means personal data processing stays in Europe. For UK SMEs running customer data through automation workflows this resolves the GDPR question. Zapier processes on US servers and does not offer EU hosting.

MIGRATION 8: STAYED ON ZAPIER

Four two-step zaps. Non-technical team. Genuine resistance to change. Staying on Zapier was the right call.

COST COMPARISON AT UK SME VOLUMES

10,000 tasks per month: Zapier Professional 149 pounds. Make.com Core 16 pounds. n8n Cloud 50 pounds. n8n self-hosted 8 pounds.

50,000 tasks per month: Zapier 382 pounds. Make.com Teams 29 pounds. n8n Cloud still 50 pounds (no task limit on cloud). n8n self-hosted still 8 pounds.

Full UK comparison: softomatesolutions.com/blog/zapier-alternatives-2026/

How we built a WhatsApp AI chatbot for a London estate agency using n8n and OpenAI in 48 hours

Softomate solutions — Mon, 08 Jun 2026 10:21:29 +0000

A London estate agency with three branches was receiving more than 80 WhatsApp messages every day. Two staff members were handling all of them manually. Average response time was four to six hours. Enquiries were going cold.

They needed a system that responded immediately, handled common questions without human involvement, booked viewings into the calendar, and passed anything complex to a human agent. We built it in 48 hours of actual build time spread across one week.

THE STACK

WhatsApp Business API via 360dialog. We chose 360dialog over direct Meta API because it offers EU-hosted data processing (UK GDPR compliance) and has more reliable webhook delivery.

n8n self-hosted on a Hetzner CX22 VPS at 8 pounds per month. All orchestration lives here: receiving webhooks, retrieving conversation history, routing, and sending replies.

GPT-4o-mini for standard queries. GPT-4o for qualification and pricing conversations. We route based on message complexity detected by a classification step.

Airtable for property listings database, synced every four hours via Airtable API.

Google Calendar API for real-time viewing slot availability.

HubSpot API to log every conversation as a contact note.

THE N8N WORKFLOW

Incoming message arrives at the 360dialog webhook and triggers the workflow. Message text is at body.entry[0].changes[0].value.messages[0].text.body.

Conversation history stores in Redis using phone number as the key. Each trigger retrieves the last six exchanges and formats them as a messages array for OpenAI. Six turns is enough context for a property enquiry conversation.

Classification step runs first using GPT-4o-mini with this prompt: Classify this WhatsApp message as one of: PROPERTY ENQUIRY, BOOKING REQUEST, PRICING QUESTION, COMPLAINT, GENERAL. Output only the category label. That label routes the workflow to one of five branches.

BOOKING REQUEST branch: extract date and time preference from message, check Google Calendar, book if available, send confirmation via 360dialog. Full sequence under 90 seconds.

PROPERTY ENQUIRY branch: query Airtable for matching properties based on area or reference number mentioned, format results as readable message, send reply.

GENERAL branch: send full message with conversation history and system prompt to GPT-4o, return response.

THE SYSTEM PROMPT

You are a professional letting agent assistant for [Agency Name]. Help prospective tenants with property enquiries, viewing requests, and tenancy questions. Help landlords with management queries. Respond in professional UK English only. Never invent property details. If you do not have specific information, say you will check with the team and someone will be in touch within two hours. If the caller mentions a complaint, a legal matter, or asks to speak to a person, respond with this message exactly and trigger the escalation workflow: I am transferring you to a member of our team right now. They will be with you shortly.

The escalation instruction is the most important line in the prompt. Without it the AI attempts to handle complaints and legal queries, which creates liability.

RESULTS AFTER MONTH ONE

Response time: four to six hours down to under 90 seconds, 24 hours a day. Sixty-eight percent of enquiries resolved without human involvement. Twenty percent converted to booked viewings directly through WhatsApp. Running cost: 51 pounds per month (VPS hosting plus 360dialog plus OpenAI tokens combined).

WHAT WE WOULD CHANGE

Use GPT-4o for all qualification branches, not GPT-4o-mini. The mini model occasionally misreads ambiguous phrasing around rent negotiation. The cost difference per month is small. The risk of losing a tenancy from a misread message is not.

Full service details: softomatesolutions.com/ai-chatbot-development-service-london/