Here is a quick look at the workflow behind my Al-powered WhatsApp hotel assistant. When a custom...Here is a quick look at the workflow behind my Al-powered WhatsApp hotel assistant. When a custom...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Here is a quick look at the workflow behind my Al-powered
WhatsApp hotel assistant.
When a customer sends a message, n8n receives it via a webhook and checks Airtable to determine whether the customer already exists. Based on the result, the workflow either continues the conversation or creates a new customer record.
The Al agent (powered by Gemini) responds using the hotel's knowledge base. If it can't answer a question, it intelligently offers to connect the customer with a human staff member.
If the customer accepts, the workflow notifies the team through Green API (WhatsApp), logs everything in Airtable, and waits for staff confirmation. If no one confirms within 5 minutes, the customer automatically receives a form to ensure no request is missed.
Tools used: n8n • Airtable • Green API • Google Gemini
This is just a high-level overview. I will be sharing a full voiceover walkthrough of the entire workflow in my next post, explaining every node and the logic behind it. Stay tuned!
Most people don’t avoid automation because they lack ideas.
They avoid it because turning “when this happens, do that” into a working system can swallow an afternoon.
n8n has just introduced an assistant that can take a plain-English request, build the workflow, run it, and help fix what breaks.
That makes the first step easier. But there’s still one thing the tool can’t decide for you: what should happen when reality doesn’t follow the happy path.
Before automating a task, write down:
What starts it?
What should happen?
When should a person step in?
If you could automate one annoying task this week, what would it be?
Building the Canadian Tariff Defence Hub in Under 7 Days: Claude MCP & Gemini Workflow
Overview
When Canada’s new counter-tariff schedules landed, Canadian business owners needed immediate clarity on line-item exposure and relief options. To respond at speed, our team built and launched the Canadian Enterprise Tariff Defence Hub end-to-end in less than a week.
The Challenge
We needed to translate complex trade policy, tariff schedules, and government relief programs into custom, plain-English business audits. The objective was to build a full web platform and an automated backend artifact generator without spending weeks on manual CMS administration or document formatting.
How We Built It
Claude MCP to WordPress Integration: We used Claude connected via Model Context Protocol (MCP) directly to our WordPress environment. This allowed us to generate, format, structure, and deploy complex pages, custom intake funnel steps, and technical copy without touching the native UI or performing manual page layout work.
Gemini & NotebookLM Package Pipeline: To power the audit deliverables, we engineered a pipeline using Gemini models to process business inputs, invoices, and supplier catalogues. This architecture automatically generates full multi-format client packages—including impact reports, slide decks, one-page visual infographics, and synthesized audio overviews for business owners on the go.
Rapid Intake Architecture: Integrated automated payment tiers (including local Nanaimo discounts and flexible options) tied directly into our 48-hour delivery workflow.
The Result
A fully operational, production-grade service platform built from concept to live deployment in under 7 days, capable of ingesting raw client trade data and outputting comprehensive, multi-media analysis packages instantly.
The rapid intake architecture is a smart touch—turning complex tariff inputs into a clear, usable workflow in under a week is impressive. The multi-format audit outputs sound especially practical.
I automated my entire customer onboarding process using one n8n workflow.
Dropping the ball on day one costs you lifetime customers.
You close a deal. The client is excited.
Then your team forgets to send the welcome package.
Or you pay a customer success manager $70k a year to manually trigger emails and update the CRM.
It is a slow, expensive bottleneck.
I stopped relying on human memory for week-one operations.
Here is exactly what this architecture executes:
→ Data Capture: A webhook catches the new signup and validates the client info.
→ Instant Action: It builds the HubSpot profile and alerts the team via Slack.
→ Time-Delay Sequences: Welcome email instantly. Docs at hour 2. Check-in at day 1. Success guide at day 3.
→ The Loop: It updates the CRM status the moment onboarding is complete.
Here is the ROI:
→ Zero manual admin work for your team
→ Flawless, professional first impressions
→ Week-one client churn dropped to absolute zero
If you want to work with me to build a similar automation in your business, I have a few spots open in my calendar this month.