2025.12.0

🚀 Introducing Workflows — Turn your data platform into an Automation engine

We keep updating records manually after every change.

One missed step breaks the entire process.

Our team spends more time coordinating than executing.

As teams and data grow, manual follow-ups don't scale. Records get updated late, notifications are missed, and processes depend on people remembering what to do next.

Introducing Workflows in NocoDB.

Workflows let you automate actions based on data changes, so your system responds instantly—without manual intervention. From record updates and notifications to integrations and conditional logic, workflows help you turn data events into reliable automation.

Workflows (beta) are available on NocoDB Cloud (all plans) and licensed on-premise deployments. In NocoDB Cloud, availability of specific workflow nodes depends on your plan.

🌟 Why This Matters — Built for an Agentic Future

With Workflows, your data doesn't just sit in tables waiting for humans to respond—it drives action.

Before: Human-Driven Systems

• Teams react after changes happen
• Manual steps slow down operations
• Missed follow-ups cause delays and errors

After: Data-Driven, Agent-Ready Automation

• Actions trigger instantly when data changes
• Processes run consistently, every time
• Less manual coordination, fewer mistakes

🔒 What This Enables

• A foundation for autonomous, event-driven systems
• Reliable handoffs between humans, automations, and future AI agents
• Deterministic execution with full visibility and control
• Automation you can trust as complexity grows

Workflows move NocoDB beyond automation as a feature— they make it an execution layer for agentic systems.

🔍 Visibility & Control

Each workflow run is recorded with execution logs, showing:

• What triggered the workflow
• Steps executed and their status
• Timing and outcomes

This ensures workflows remain transparent, auditable, and reliable as usage grows.

Workflows turn NocoDB into more than a database—they make it a reliable automation engine for everyday business processes. Reduce manual work, improve consistency, and let your system respond automatically to change. Learn more.

🚀 Introducing Unique Fields — Keep Your Data Clean, Accurate, and Trustworthy

We ended up with duplicate email IDs, and now automations are breaking.

Usernames were supposed to be unique, but duplicates slipped in and reports became unreliable.

As your data grows, duplicates become silent problems. Two records with the same email; same phone number reused; same identifier pointing to different entities. These issues don't just clutter your tables—they break integrations, automations, and trust in your data.

Introducing Unique Fields in NocoDB.

With a single setting, you can now enforce uniqueness at the field level, ensuring that critical identifiers remain truly unique across records—by design, not by convention. Whether it's email addresses, usernames, order IDs, or reference numbers, Unique Fields help you prevent errors before they enter your system.

Feature available on NocoDB Cloud Business plan onwards, and on self-hosted Enterprise editions.

🌟 Why This Matters

Before:

• Duplicate identifiers creeping into tables
• Broken automations and inconsistent reports
• No reliable guardrails at data entry time

After:

• Enforce uniqueness directly at the field level
• Errors caught instantly—before records are saved
• Cleaner data for integrations, APIs, and workflows
• Stronger guarantees for IDs, emails, and key attributes

🔒 How Unique Fields Work

Enable Unique values only while creating a field. Once enabled:

• NocoDB blocks duplicate non-empty values; empty cells are allowed
• Validation happens on every create and update
• Users see a clear error message if a duplicate is entered

📌 Supported Field Types

Uniqueness can be enforced on commonly used identifiers, including:

• Single line text
• Email, Phone number, URL
• Number, Decimal, Currency, Percent
• Date, Time, DateTime

⚠️ Things to Know

• Best used where uniqueness is critical—large datasets may see performance impact
• Works only for tables created within NocoDB (NC-DB)
• Existing field data must already be unique before enabling

Unique Fields give your data a built-in integrity layer—simple to enable, powerful in impact. Stop fixing duplicates after the fact, and start preventing them at the source. Learn more.

🚀 Introducing Table Visibility — Control Who Can See Your Tables

Some teams shouldn't even know this table exists.

I want to hide internal or sensitive tables without breaking related data.

As bases grow, not every table is meant for everyone. Internal configs, admin-only datasets, background reference tables—these often clutter the workspace or expose structure that certain users were never meant to see.

Introducing Table Visibility in NocoDB. A new layer of control that lets you decide who can see a table at all—before any permissions on records even come into play.

Feature available on NocoDB Cloud Team plan onwards, and on self-hosted Enterprise editions.

🌟 Why This Matters

Before:

• All tables visible to everyone by default
• Sensitive or internal tables cluttering the workspace
• No way to hide tables without restructuring bases
• Confusion over "read-only" table data vs "shouldn't see this at all"

After:

• Decide who can see a table—explicitly
• Hide internal or sensitive tables from specific roles
• Cleaner, role-focused workspace experiences
• Visibility evaluated before any record-level permissions
• Predictable behaviour across UI, APIs, Automations, and Extensions

🔐 Visibility Options

You can control table visibility using simple, role-based options:

• Everyone (default)
• Editors & up
• Creators & up
• Specific users or teams

This lets you align your base structure with how your organisation actually works.

⚙️ How It Works in Practice

• Visibility is checked before record permissions
• Hidden tables:
• Don't appear in the sidebar
• Aren't accessible via APIs, Automations, Scripts, or Extensions
• Are excluded when duplicating a base (if the user can't see them)

Even when hidden, related data remains safe:

• Lookup and Rollup fields continue to work
• Relational fields show display values without exposing the table

Table Visibility is a foundational step toward cleaner access control and better data boundaries—so users see exactly what they need, and nothing they don't. Learn more.

🌙 Introducing Dark Mode — A More Comfortable Way to Work

After a few hours of working with data, my eyes feel strained.

I prefer a darker interface when working late

Spending long hours inside NocoDB shouldn't come at the cost of visual comfort. Whether you're reviewing data, building views, or configuring workflows, the interface should adapt to how you prefer to work.

Introducing Dark Mode in NocoDB. A manually configurable dark theme designed to reduce eye strain and improve focus during extended or low-light work sessions.

🌟 Why This Matters

Before:

• Bright interface during long or late-night sessions
• Increased eye fatigue when working with large datasets
• No visual alternative for users who prefer darker UIs

After:

• Optional Dark Mode you can explicitly enable
• Reduced glare for long working hours
• Improved contrast for data-dense screens
• A calmer, more focused visual experience

Dark Mode puts visual comfort in your control—so you decide how NocoDB looks and feels while you work. Try it today!

Learn more.