NocoDB

NocoDB

RELEASE NOTES

2026.04.5

FEATURE RELEASE · APRIL 2026

2026.04.5 : Base Trash, Mailchimp Workflows & PostgreSQL ENUM

Base Trash now restores deleted tables, views, and fields too. Mailchimp joins Workflows as a first-class integration. And PostgreSQL ENUM columns from external sources now appear as SingleSelect fields.

BASE TRASH

Base Trash is the single, unified safety net for everything inside a base. With this release, it expands beyond records to cover structural recovery: deleted tables, views, and fields can now be restored from the same Trash UI, with every record, formula, link, comment, and configuration that lived inside them put back exactly as it was.

Whether you're recovering from a misclicked Delete table, restoring a column someone trimmed during a cleanup, or rolling back a view a teammate dropped from the sidebar, Base Trash puts the structure back in a click. One Trash, one click, full recovery.

Availability: all cloud plans and on-premise Enterprise. Per-base retention and the ability to disable Base Trash on selected bases is Enterprise-only.

MAILCHIMP IN WORKFLOWS

Mailchimp joins HubSpot CRM, Twilio, and GitHub as a first-class integration inside Workflows, so your records can trigger campaigns, sync your audience, and send transactional emails without ever leaving NocoDB. Whether you're turning a CRM table into a daily-synced Mailchimp audience, kicking off a welcome campaign the moment a new sign-up lands in your base, or tagging contacts based on form responses or lifecycle stage, the Mailchimp node replaces the brittle webhook glue most teams stitch together today.

What's covered: Campaigns (Create, Get, Update, Delete, Send, List), Contacts (Add, Get, Update, Delete), Contact tagging, and Transactional email.

POSTGRESQL ENUM SUPPORT

PostgreSQL ENUM columns from external Postgres sources now show up as SingleSelect fields inside NocoDB. One of the most upvoted requests from the community (#4862), this closes a long-standing gap for teams who connect NocoDB to a Postgres database where ENUMs already define the allowed values.

Whether you're sharing a database between an application that writes ENUM values and a team that edits them in NocoDB, building dashboards over a schema your engineering team owns, or just preferring to keep the source of truth in the database, ENUM columns behave like any other SingleSelect — values render as coloured chips, the picker is restricted to the labels defined in Postgres, and edits round-trip back without breaking the ENUM type.

Read ENUM columns as SingleSelect, edit values from any view, and add / rename / remove options directly from NocoDB — changes apply to the underlying Postgres ENUM type. Filter, sort, group, and search exactly like SingleSelect.

ALSO IN THIS RELEASE

  • Faster base load on large schemas, with table metadata streamed in as you scroll the sidebar.
  • CSV export honours active filters, exports now match exactly what the view shows.
  • Workflow run history pagination no longer skips the most recent run on heavily-used workflows.
  • Realtime LTAR updates, linking or unlinking on row-level-secured bases now reflects across users instantly.
Read the Full Changelog

What should we build next? Hit reply and tell me. I read every response personally.

NocoDB Inc. · nocodb.com

cloud · enterprise