Analysis updated 2026-05-18
Automate realistic looking back and forth email replies to build up a new inbox's sending reputation.
Warm up multiple Gmail or Outlook sender inboxes at once on a business hour schedule.
Use AI generated content so warm up conversations sound more natural than single canned replies.
Adapt the workflow templates to your own domains and email accounts.
| zakaria-systems/ai-email-warmup-workflows | 0labs-in/vision-link | 1038lab/agnes-ai | |
|---|---|---|---|
| Stars | 4 | 4 | 4 |
| Language | — | TypeScript | Python |
| Setup difficulty | — | moderate | easy |
| Complexity | — | 3/5 | 2/5 |
| Audience | pm founder | developer | vibe coder |
Figures from each repo's GitHub metadata at analysis time.
This project is a collection of automation workflows built with n8n, a visual workflow automation tool, designed to warm up email inboxes. Warming up an inbox means gradually building a sending history of normal looking activity so that email providers trust the account more and its outgoing messages are less likely to be marked as spam. Most simple warm up tools just send one email and get one automatic reply back. This project aims to go further by using AI generated content to simulate more realistic, natural sounding email conversations, including multiple back and forth replies rather than a single exchange. It includes ready made workflows for automatically replying to messages in both Gmail and Outlook, sends messages during normal business hours, adds random delays between messages so the timing looks human rather than robotic, and supports warming up multiple sender inboxes at once. The author describes the architecture as ready to connect to analytics tools, though the repository itself does not include an analytics dashboard. The stated long term goal is to scale this same approach up to hundreds or even thousands of inboxes while still keeping the simulated conversations looking realistic. The README is short and the repository is explicitly described as a sanitized public version, meaning any credentials, sensitive data, or private information used in the author's own setup have been stripped out before publishing. Because of that, a user would need to supply their own email accounts, n8n instance, and any AI service credentials to actually run these workflows themselves. No license or specific tech stack beyond n8n is stated in the README.
This repo across BitVibe Labs
Verify against the repo before relying on details.