Capture leads on WhatsApp and save them to Sheets
An n8n WhatsApp agent asks leads for their name and email and automatically saves them to Google Sheets, shown in a demo.
Claude Cowork scans email and LinkedIn inboxes and replies to outreach responses, while another workflow writes first lines from prospect site and LinkedIn research.
Claude Cowork scans email and LinkedIn inboxes and replies to outreach responses, while another workflow writes first lines from prospect site and LinkedIn research.
One commenter said they switched from Claude Code to Claude Cowork and connected it to their Gmail or Apollo-sent mailbox through MCP, plus enrichment tools including Apollo, Clay, Zero Bounce, LinkedIn, and LinkedIn Jobpost. Claude Cowork scanned email every 10 minutes and LinkedIn inboxes through Phantombuster every 60 minutes, then replied to outreach responses or expressions of interest automatically.
The thread gives no hard numbers for this specific setup, only that the commenter uses it to answer interested replies from email and LinkedIn. The source does not describe approval steps or where a human reviews messages before sending.
The clearest catch is the stack complexity: it depended on MCP connections plus Phantombuster polling LinkedIn every hour and email every 10 minutes.
Go through my [email and LinkedIn] inbox for replies to my outreach campaign about [product/offer]. Sort them into interested, not interested, and needs follow-up, and draft a reply for each in my voice: [tone description]. Show me all the drafts together and wait for my approval before sending any message.
An n8n WhatsApp agent asks leads for their name and email and automatically saves them to Google Sheets, shown in a demo.
An n8n agent handles customer WhatsApp messages, searches info, checks the calendar, logs to Sheets or Notion, and replies by WhatsApp and email.
A Lindy agent researches YouTube ideas and scripts, and another emails a brief on discovery-call contacts 10 minutes before meetings; complex content stayed on Make.