Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.3
This workflow is provided as-is. Please review and test before using in production.
Inspiration & Notes This workflow was born out of a very real problem. While writing a book, I found the process of discovering suitable literary agents and managing outreach to be manual, and surp...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.stickynote, n8n-nodes-base.switch, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.memorybufferwindow, n8n-nodes-base.code, n8n-nodes-base.gmail
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by malcolm.
Original n8n.io sourceThis workflow was born out of a very real problem.
While writing a book, I found the process of discovering suitable literary agents and managing outreach to be manual, and surprisingly difficult to scale. Researching agents, checking submission rules, personalizing emails, tracking submissions, and staying organized quickly became a full-time job on its own.
So instead of doing it manually, I automated it.
I built this entire workflow in 3 days — and the goal of publishing it is to show that you can do the same. With the right structure and intent, complex sales and marketing workflows don’t have to take months to build.
If you have questions, business inquiries, or would like help setting up automation workflows, feel free to reach out:
I genuinely enjoy designing workflows and automation systems, especially when they support meaningful projects. I work primarily from interest and impact rather than purely financial motivation.
Whether I take on a project for FREE or paid for the following reasons:
If you’re building something thoughtful and need help automating it, I’m always happy to have a conversation. Enjoy~!
Automates the end-to-end literary agent outreach pipeline, from data ingestion and eligibility filtering to deep agent research, personalized email generation, submission tracking, and analytics.
The system is organized into four logical domains: The system is modular and is divided into four domains:
--> Data Engineering --> Marketing & Research --> Sales (Outreach) --> Data Analysis
Each domain operates independently and passes structured data downstream.
Purpose:
Ingest and normalize agent data from multiple sources into a single source of truth.
Inputs
Key Steps
Output
Purpose:
Decide who to contact and how to personalize outreach.
An AI agent evaluates each record against strict rules:
Outputs
send_email (boolean)reason (auditable explanation)For eligible agents only:
Strict Rule:
All claims must be explicitly cited; no inference or hallucination is allowed.
Purpose:
Execute personalized email outreach and maintain clean submission tracking.
Steps
Submission CompletedSubmission TimestampResult
Purpose:
Measure pipeline health and outreach effectiveness.
Features
Supports
This workflow is production-ready, modular, and designed for extension into other sales or marketing domains beyond literary outreach.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 54 workflow blocks. Download the JSON for the full node graph.
| Workflow | Qualify and email literary agents with GPT‑4.1, Gmail and Google Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 54 |
| Categories | Lead Generation, AI RAG |
| Author | malcolm |
| Published | 12 Jan 2026 |
Use the JSON export at /data/workflows/12651/12651.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Inspiration & Notes This workflow was born out of a very real problem. While writing a book, I found the process of discovering suitable literary agents and managing outreach to be manual, and surp...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation, AI RAG use case.