DE EN IT

~/home / inbox-beast

🐾 n8n · Nextcloud · live

The Inbox Beast.

Unanswered mail makes it hungry. One click and an n8n workflow reads an inbox from Nextcloud, sorts every mail into do, delegate or ignore, computes the beast's hunger (five stages, from egg to kraken) and really creates cards in Deck, a message in Talk and a report in Files.

Colour

🔒 It only reads one dedicated demo mailbox in the Nextcloud Mail app, with invented mails of the fictional Brightside Studio. A guard checks account and address, so nobody sees real mailboxes here. For your own inbox, enter your account and mailbox ids in the first Code node.

The file only contains placeholders (address, user, credentials). You cannot import it as it is: enter your own credentials and IDs first.

How it works

  1. WebhookYour click starts an n8n workflow on my server. The page only sends a colour and two numbers for the simulation.
  2. Fix the demo spaceA Code node defines where the workflow may read and write: one mail account, one Deck board, one Talk room, one folder. Every URL is checked against it.
  3. Three requests at onceThe Mail API fetches the messages of the demo mailbox, the Deck API the board, a PROPFIND lists the Outbox folder.
  4. Rules firstA Code node sorts every mail into do, delegate or ignore with fixed rules and gives it a priority. It works without AI.
  5. AI assistantA language model hosted at IONOS in Germany corrects the sorting and writes the report, the quote and the tip. Every answer is validated: invalid categories or invented people are dropped.
  6. Hunger and stageFrom the unanswered mails and their age a Code node computes hunger (0 to 100%) and the stage from egg to kraken. The dials simulate what happens when you reply or do nothing.
  7. WriteDeck API: up to five cards. WebDAV PUT: a report as Markdown. Talk API: one message. Before that, the workflow deletes its own earlier cards and the oldest reports.
  8. IngestThe result, with the real status codes of the writes, lands on the server as JSON. This page builds the beast from it.

Privacy: nothing of yours is sent to Nextcloud, the workflow only works with the fictional demo data. The result is stored (with no link to you) so the share link works, plus, for the limits, a salted hash of your IP address for at most one hour. More in the privacy policy

To keep Nextcloud relaxed: 20 seconds between two runs, three per hour and visitor, 100 per day.

How the workflow is built: the article →

More n8n workflows to try →