tl;dr "Agents" sound intimidating, but the smallest useful one I’ve built fits neatly into a five-node n8n workflow that runs every Monday, creates fresh marketing ideas for BoxBoard, and stores them for later use.


1. Wait—what is an “agent”?

If you’ve opened LinkedIn or Product Hunt in the last year, you’ve heard

“Our platform now supports agents!”

Under the hood, most of those agents are just workflows that contain at least one step where an LLM makes a decision:

That’s it. 90 % plumbing, 10 % AI.


2. My use-case: weekly marketing inspiration

Every Monday I used to spend 20 minutes brainstorming LinkedIn ideas for BoxBoard. That’s precisely the kind of low-leverage chore automations love.

The initial 4-node proof-of-concept

  1. Cron Trigger – fires at 08:00 on Mondays
  2. OpenAI – “Give me 10 marketing post ideas for BoxBoard.”
  3. Code – turn the JSON into rows
  4. Postgres Insert – save into marketing_ideas

It worked! But after week two the model repeated itself—classic LLM amnesia.

The current 5-node version

(Screenshot below)

  1. Cron Trigger
  2. Postgres Select – pull last week’s ideas
  3. OpenAI“Give me 10 *new** ideas not found in this list…”*
  4. Code – format rows
  5. Postgres Insert – write the fresh set

n8n workflow: cron → Postgres select → OpenAI → code → Postgres insert


3. Why Postgres and not Sheets / Airtable?

Use whatever datastore fits your stack, but SQL saves future you a refactor.


4. Extending the agent


5. Takeaways

  1. Small is beautiful. An “agent” can start with one LLM call and still deliver real value.
  2. Think like a PM. Break ambitious ideas into tiny shippable tasks; wire them; iterate.
  3. Data matters. Choosing a real database early unlocks smarter prompts and future automation layers.

Where could a five-node flow erase your Monday busywork?


Questions or war stories about your own tiny agents?
Ping me on Twitter—always happy to swap notes.