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
Back to feedPost
Designed and developed an AI-powered WhatsApp chatbot for a padel court booking business. The chatbot allows customers to book courts, check availability, manage reservations, and receive instant responses through WhatsApp.
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
Related posts
Obviously automated
Lost 2 days building a complex n8n workflow. Here's what I learned.✌️
The project: A 12-node AI Receptionist automation for a luxury resort in Bangladesh. Multi-channel (WhatsApp, Telegram, Voice), 9 Google Sheets, Gemini API, payment automation, customer CRM.
What went wrong: Added a new voice integration node. Accidentally deleted the entire workflow.
Why it happened:
No JSON exports after milestones
No version control (Git)
Testing changes LIVE on production workflow
No documentation
Building locally with zero redundancy
The fix (now implemented):
✅ JSON backups after every 2-3 nodes
✅ GitHub versioning
✅ Clone workflows for testing
✅ Modular design
✅ Complete documentation
For automation professionals: You're not just builders—you're engineers.
Treat workflows like software:
Documentation
Version control
Backup strategy
Modular testing
Client delays = lost revenue + credibility damage.
Make the systems bulletproof.
How do you prevent data loss in your automation builds? 👇
#n8n #Automation #WorkflowAutomation #NoCode #LessonsLearned #make #AIAutomation #DataAnalyst #MachineLearning
I'd try restoring one of those JSON backups into a cloned workflow before the next handoff. That way you know it can actually get you running again.
Built an AI-powered Slack bot that manages inventory and orders directly from chat — no spreadsheet switching required.
The team needed a faster way to check stock and log orders without leaving Slack. I built a Make.com scenario that:
Watches Slack for new messages
Passes the message to a Make AI Agent, which interprets the request (check stock, place an order, update inventory)
The AI Agent searches inventory, creates orders, or updates stock levels in Google Sheets depending on intent
Sends the answer straight back to Slack as a reply
Result: The team can now manage inventory and orders with a simple Slack message — the AI Agent handles the logic and Google Sheets stays updated automatically, with zero manual lookups.
Tools: Slack, Make AI Agents, Google Sheets (built on Make.com)
