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
Just shipped: Telegram → Google Sheets auto-logger with n8n
No more copy-paste. Bot receives message → parses phone/email → hash checks duplicate → appends to Sheet with timestamp + user ID.
Stack: n8n + Telegram Bot API + Google Sheets API
Result: 5 hrs/week saved for a sales team
I build these micro-automations daily. Need one for your team?
#aiworkflow #n8n #telegram #automation #chatbot
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
Shopify Abandoned Cart Recovery Automation 🛒
Ever wondered how many potential orders an online store could miss when customers add products to their cart but leave without completing checkout?
I built an abandoned cart automation workflow using Activepieces, Shopify, Google Gemini, Gmail, and WhatsApp Business.
⚙️ How It Works
🛒 Cart Trigger: Detects an abandoned checkout event from Shopify.
🔀 Conditional Routing: Routes the workflow based on configured conditions.
🤖 AI-Powered Messaging: Gemini generates a personalized reminder message.
💬 WhatsApp Reminder: Sends a cart reminder through WhatsApp Business.
📧 Email Reminder: Sends a follow-up email to encourage the customer to complete checkout.
💡 How It Can Help E-commerce Businesses
Remind customers about products left in their carts.
Reduce repetitive manual follow-up work.
Make customer communication more consistent.
Create an opportunity to recover potentially lost sales.
Tools Used: Activepieces | Shopify | Google Gemini | Gmail | WhatsApp Business
Project Type: Personal Automation Project
I built this workflow to demonstrate how automation can support abandoned cart recovery for Shopify and D2C businesses.
Interested in automating your store's customer follow-ups? Let's connect.
The 30–60 minute delay then 24-hour follow-up is a sensible cadence. The part I would harden next is the stop conditions: once the cart converts or the customer replies, every channel should cancel, and WhatsApp especially needs a clear opt-in trail before the first send....
Processing incoming PDF attachments and logging key email data manually takes hours of tedious, repetitive work. Every time a new invoice, quote, or report lands in your inbox, you have to manually open the email, download the PDF, read through dense pages to extract important details, format the data, and log it into Google Sheets row by row.
Which one is faster, saves more time, and prevents mistakes?
1 voted
25%
3 voted
75%
4 votes
Closed
The manual-vs-automated framing is clear, but I'm curious how the workflow copes with PDFs that don't share a layout, like scanned invoices versus quotes. Do you parse them with a fixed template or an extraction step, and what happens to rows it can't read confidently?
I’ve been working on a small skill called Manual Orchestrator to make longer projects with AI agents easier to manage.
The problem started with a familiar situation: one chat would accumulate plans, implementation details, corrections, and test results. By the time I was ready for the next phase, I wanted a fresh conversation without losing the decisions we’d already made.
Manual Orchestrator gives that process some structure. One chat acts as the orchestrator: it breaks the work into stages and writes a prompt for the next one. I run that prompt in a new session, then bring the result back. The orchestrator reviews it against the stage’s criteria before preparing the next prompt. If something needs fixing, I go back to the same worker session.
The skill also keeps a record in the project with the current stage, decisions, evidence, and next steps. That makes it easier to pause, resume, or hand the work to another session.
The handoff is manual. I choose when to open a session and carry the result back. The orchestrator and worker sessions can also use different agent CLIs, with the prompt adapted to the capabilities available.
It’s open source and still a work in progress. I’m using it to learn what helps in practice and where the workflow needs to improve. Installation has been checked for Codex, Claude Code, and Gemini CLI, but the full workflow hasn’t been tested across every CLI or version.
If you try it, I’d be interested in hearing what works and where it gets in your way.
