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.
An agent loop reading a revenue dashboard ran 365 cycles, generating 394 interlinked SEO pages and a webhook inspection tool with landing page, docs and drafted outreach.
An agent loop reading a revenue dashboard ran 365 cycles, generating 394 interlinked SEO pages and a webhook inspection tool with landing page, docs and drafted outreach.
The agent was told to make real money and ran every 20 minutes. Each cycle it read a dashboard of revenue, products and decisions, and it read a tenet file of rules it could not edit. It then picked an action, built or shipped something, and appended its reasoning to a decision log. Over 365 cycles it produced the SEO pages and the webhook tool.
Revenue was $3, from one coffee purchase prompted by a story about the project rather than by the tools. The 394 pages earned nothing, and distribution stayed unsolved. The agent then pivoted on its own to build-in-public writing.
The tenets, including never spending money without approval and preferring one thing done well, kept the agent in check, and it had no budget or audience to draw users.
Help me build a small [type of tool, e.g. webhook inspector] with a landing page and docs, plus a set of [number] interlinked SEO pages around [topic] in [folder or repo]. Work in short cycles: generate pages, check links and quality, then improve. Stop after [number] pages and a summary of what you made, and show me any outreach drafts instead of sending them, and ask before deploying anything.
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.