Purge n8n execution history located in Mysql

Needs changes

by Miquel Colomer ✓ · 2,458 views · created 2020-10-04 · DevOps

Needs changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.

What this workflow does

This workflow has 3 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects MySQL.

How it runs

Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).

MySQL: run a query

Services it uses

MySQL

Before you upgrade to n8n 3.0

1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:

Cron: replace with Schedule Trigger.

Removed in 3.0	Replace with
Cron Cron	Schedule Trigger

Nodes used (3)

Manual Triggern8n-nodes-base.manualTrigger
MySQLn8n-nodes-base.mySql
Cronn8n-nodes-base.cron

From the author

This workflow is useful if you have lots of tasks running daily. MySQL node (or the database used to save data shown in n8n - could be Mongo, Postgres, ... -) remove old entries from executionentity table that contains the history of the executed workflows.…
Excerpt from Miquel Colomer's description on n8n.io.

View the original on n8n.io → Check your own copy

Purge n8n execution history located in Mysql

What this workflow does

How it runs

Services it uses

Before you upgrade to n8n 3.0

Nodes used (3)

From the author

Get the weekly “what broke” email