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
Gmail Campaign Automation with Auto Follow-Up (Gmail API + n8n). Sends personalized outreach at scale, tracks who replies, and follows up on its own if there's been no response — no one has to remember to check.
Replaces a manual process where outreach was sent one at a time with no reliable way to track who needed a follow-up — meaning warm leads often went cold simply because nobody circled back in time. This automation bulk-sends personalized emails through Gmail, checks reply status automatically, and sends a follow-up on its own after a set number of days to anyone who hasn't responded. Skips weekends so follow-ups land at sensible times.
Currently live for 3–4 agency clients.
Good fit for: sales teams and agencies running cold or warm outreach campaigns who don't want a person manually tracking a spreadsheet of who replied.
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.
Automated a manual Google Sheets → Slack workflow to eliminate repetitive data entry and give the team instant notifications.
Previously, new data had to be manually checked, processed, and shared across the team — slow and easy to miss. I built a Make.com scenario that:
Watches Google Sheets for new/updated rows
Processes and routes the data through a router based on conditions
Creates corresponding Trello cards for task tracking
Logs processed records back to Google Sheets
Sends real-time Slack notifications so the team is instantly updated
Result: What used to be manual checking and updating is now fully automated — saving hours weekly and removing room for human error.
Tools: Make.com, Google Sheets, Trello, Slack
wow love this