n8n Error Workflows That Actually Alert: Deduplication, Stale Locks and the Friday Email
Part 6 of the series: how the machine reports that it is broken, why an empty email every Friday is part of that, and the failure it still cannot report.
Work that comes back every week? No human needed. More on AI and automation
All blog posts tagged PostgreSQL.
Part 6 of the series: how the machine reports that it is broken, why an empty email every Friday is part of that, and the failure it still cannot report.
Part 5 of the series: summarising a deal's recent emails with Mistral in n8n, storing the result in Postgres, and the bugs that only real text revealed.
Part 4 of the series: the 45-node workflow at the centre of the system, and the three ways it stalled on the runs where there was nothing to do.
Part 3 of the follow-up machine series. Receiving EspoCRM stage changes in n8n, verifying the signature properly, and four mistakes that each cost real time.
Part 2 of the follow-up machine series: five n8n workflows that share one Postgres database, never call each other, and are all safe to run twice.