Reddit

Title: NocoDB 2026.04.5 - Base Trash adds structural recovery, Mailchimp joins Workflows, PostgreSQL ENUM support for external sources

Body:

Hey r/NocoDB,

2026.04.5 is out. Three things worth pulling out:

1. Base Trash now supports structural recovery

Last release we added Record Trash so any deleted row was one click away from being restored. With 2026.04.5 we extend the same Trash UI at the base level to cover structure: deleted tables, views, and fields are now recoverable from the same place. Restore a table and you get back every record, formula, link, comment, and configuration that lived inside it.

This is the same model Airtable and Baserow users already expect: one Base Trash, one click, full recovery (rows and structure together) instead of separate paths or scrambling for last night's backup.

Available on all cloud plans and on-premise Enterprise. Per-base retention controls and the ability to disable Base Trash on selected bases are Enterprise-only. Like the record-level recovery, this only applies to NocoDB-managed bases, since recovery relies on our internal storage layer.

2. Mailchimp in Workflows

Mailchimp joins HubSpot CRM, Twilio, and GitHub as a first-class Workflows integration. The node covers:

Campaigns: Create / Get / Update / Delete / Send / List
Contacts: Add / Get / Update / Delete
Contact tagging
Transactional email

Common patterns this unlocks: sync a CRM table to a Mailchimp audience nightly, kick off a welcome campaign on new sign-up, tag contacts based on form responses or lifecycle stage, send transactional receipts from a workflow.

3. PostgreSQL ENUM support (external sources)

This is one of our most upvoted issues ever (#4862) and it's finally here. If you connect NocoDB to a Postgres database that uses ENUM types, those columns now show up as SingleSelect fields in the UI. You can:

Read ENUM column values and edit them from grid, gallery, kanban, or expanded views
Add, rename, and remove options from inside NocoDB — changes apply directly to the underlying Postgres ENUM type
When the same ENUM type is shared across multiple columns, NocoDB safely forks a new type for the column being edited so your changes don't leak to siblings
Filter, sort, group, and search exactly like any other SingleSelect

Massive thanks to everyone who kept this issue alive over the years.

Plus a few quality-of-life fixes: faster base load on large schemas, CSV exports now strictly honour active filters, and a fix for the workflow run history pagination skipping the most recent run.

Full changelog: https://nocodb.com/docs/changelog/2026.04.5

Happy to answer questions in the thread.