We converted a fragile manual publishing habit into a structured, mobile-native operating system — reducing the time required to produce and ship each weekly drop from 30 minutes to 5 minutes.
What Is Drops Agent?
Drops Agent is a multi-workflow publishing system built by WalkerTrust. It automates the retrieval, drafting, scheduling, and delivery of short weekly academic reflections — called “drops.” Built on n8n and grounded in a Supabase vector store, it runs on a Telegram-native interface. The editor approves each send; the system carries the rest.
At a Glance
Challenge
A university professor with a consistent knowledge base and willing audience could not maintain a weekly publishing cadence — not due to a lack of ideas, but due to the 30-minute operational cost per drop.
Solution
Deployed a five-workflow n8n architecture — orchestrator, copy generation, email delivery, database sync, and error logging — with Telegram as the control interface and Supabase as the retrieval layer.
Results
6x reduction in active effort per drop (30 min → 5 min); full retrieval-to-delivery cycle automated; professor maintains editorial control through a structured human-in-the-loop approval step.
Why Academic Content Publishing Workflows Break Down
The professor had the intellectual raw material. He read continuously, identified relevant papers, and was fully capable of producing short weekly reflections for students and alumni. The constraint was not content quality. It was operational consistency.
Producing one drop end-to-end — choosing the topic, grounding the content, preparing publishable variants, and coordinating delivery — required roughly 30 minutes. In an academic schedule structured around classes, research, and administrative obligations, that time was rarely contiguous. A single missed week broke the cadence. And broken cadence erodes the engagement that makes the communication valuable in the first place.
How Drops Agent Automates the Academic Publishing Cycle
We designed the system around one constraint: the professor could not dedicate a fixed work block to publishing each week. The solution had to fit around his schedule — not require him to adapt to it. That framing led directly to Telegram as the primary interface, enabling creation and approval from a mobile device, in short interactions, without a dedicated session.
Layer 1 — Orchestration and Ingestion: An n8n orchestrator handles two entry modes — scheduled execution and ad hoc Telegram requests. It classifies inbound messages using an LLM-based structured parser that converts natural-language input into a normalized JSON object containing topic, audience group, date, and status. The same workflow handles document ingestion: PDFs sent via Telegram are extracted, enriched with metadata, validated, and written into the Supabase vector store. This made Drops Agent simultaneously a publishing tool and a knowledge-ingestion system.
Layer 2 — Retrieval-Augmented Copy Generation: The copy workflow separates retrieval from writing. A retriever agent queries the Supabase vector store and is explicitly constrained to use only stored content. A writer agent then generates a 50–60 word drop for a business-school audience using only that retrieved material. The loop runs three times, producing three distinct candidate versions — each stored in a staging sheet and surfaced to the professor through Telegram.
Layer 3 — Human Approval and Delivery: The professor selects one of the three versions, or requests a new set. The selected version passes to the email delivery workflow, which filters the correct distribution list from the control spreadsheet, formats the email, sends via Gmail, and updates the topic status to Shipped. An error-logging workflow captures any failures and surfaces them as Telegram alerts — keeping support overhead near zero.
Measured Results
- Active effort per weekly drop reduced from 30 minutes to 5 minutes — a 6x decrease in publishing overhead
- Full cycle — retrieval, drafting, audience routing, sending, and status tracking — automated across 5 coordinated n8n workflows
- Professor retained editorial control through a structured 3-candidate approval step before every send
- Knowledge base compounds over time: each new paper ingested via Telegram enriches the vector store and improves future retrieval quality
- Operational visibility maintained via a dedicated error logger writing to Google Sheets and pushing Telegram alerts — no secondary monitoring tool required
Before and After:
| Dimension | Before Drops Agent | After Drops Agent |
|---|---|---|
| Time per weekly drop | ~30 minutes end-to-end | ~5 minutes (review and ship) |
| Interface | Multi-tool desktop session | Single Telegram conversation |
| Content grounding | Manual selection and context | Automated vector store retrieval |
| Publishing consistency | Dependent on available time blocks | System-maintained cadence |
| Editorial control | Fully manual | Preserved via HITL approval step |
| Error visibility | None | Logged to sheet, alerted via Telegram |
Why Automation Succeeds When It Adapts to the User’s Schedule
Most automation projects fail because they ask the user to adapt to the system. Drops Agent was designed in the opposite direction.
The professor’s schedule does not include reliable 30-minute windows for administrative publishing work. The system was therefore built to require only short, mobile interactions — a topic confirmation, a version selection, a send approval. Everything else was transferred to the machine.
The achievement was converting a task that depended on uninterrupted time into a task that can be completed in under five minutes from a phone. The system now keeps the cadence. The professor now only makes the decisions that require editorial judgment.
That distinction — between operationally autonomous and editorially supervised — is what made the project usable in practice, not just functional in theory.
What Comes Next: Adaptive Ranking and Audience Analytics
With the publishing cycle automated and the knowledge base compounding, the next logical layer is feedback integration. The current system records which version the professor selects, but those selections do not yet materially influence future generation strategy.
We are scoping a preference-learning layer that uses selection history to weight generation toward the stylistic and structural patterns the professor consistently favors. Separately, tracking engagement signals — open rates, click-throughs, and audience-specific response data — would allow the system to refine both topic selection and version ranking over time.
The goal is not to remove editorial judgment. It is to make that judgment better informed.
Frequently Asked Questions
What does a human actually do in this workflow?
He initiates or confirms a topic, reviews three candidate drop versions in Telegram, selects the preferred one, and confirms the send. That is the full interaction. Everything else — retrieval, drafting, audience filtering, delivery, and status tracking — is handled by the system.
How does Drops Agent ground content in academic source material?
Papers are uploaded directly via Telegram. The system extracts the PDF, pulls metadata, allows corrections, cleans the text, and writes structured content into a Supabase vector store. The retriever agent queries that store for each new drop — constrained to use only stored material, not general model knowledge.
Why does the system generate three draft versions instead of one?
Final selection is subjective and context-dependent. Presenting three distinct candidates preserves editorial judgment at the point where it matters most — the last mile — without requiring the editor to be involved in the generation process itself.
Is Drops Agent a content generation tool?
No. Drops Agent automates the retrieval, drafting, scheduling, and delivery cycle that surrounds content. The editor’s judgment — what gets sent — remains human-controlled. The system ensures that judgment is exercised efficiently, not that it is replaced.
What happens when something fails?
A dedicated error-logging workflow captures the failure, writes it to a Google Sheets log, and sends a Telegram alert with the workflow name, failing node, timestamp, and execution URL. The professor operates in Telegram already, so the alert reaches him in the same channel as everything else. We monitor those logs as part of the engagement — infrastructure-level issues are identified and addressed before they affect the publishing cadence.
Who is Drops Agent designed for?
This model is suited to practitioners — academics, consultants, analysts — who have a consistent knowledge base and a willing audience, but cannot dedicate a weekly work block to the operational side of publishing. If the content quality is there and the bottleneck is consistency, that is the problem this architecture solves.
Work With Us
If your communication output is inconsistent — not because you lack ideas, but because the operational overhead keeps getting in the way — that is the gap worth closing. We work with practitioners and founders who want structured, automated publishing operations, not generic content tools.
To discuss where your current setup stands, contact us at pedrorcosta@walkertrust.com or connect on LinkedIn.
Pedro Ribeiro da Costa is a Partner at WalkerTrust, specialising in AI-powered process automation and digital transformation. He has led automation and intelligence initiatives across Supply Chain and Business Intelligence in environments up to €1.2B in revenue.