Add JSON (Object) and Array data types to Data Tables

Feature Requests
,
1

The idea is:

Add support for JSON (Object) and Array data types in n8n Data Tables.

Currently, Data Tables only support basic flat types: String, Number, Boolean, and Date.
Since n8n is natively built around JSON data structures, users often need to store complex objects or lists.

My use case:

I frequently need to store API responses or configuration objects in a Data Table.
Because Object and Array types are missing, I am forced to use a workaround:

  1. Write: Use JSON.stringify() to convert the object/array into a string to save it in a String column.
  2. Read: Use JSON.parse() every time I retrieve the data to make it usable in the workflow again.

Examples of data I want to store natively:

  • API response payloads (complex objects).
  • Lists of tags or IDs (arrays).
  • User configuration metadata (nested JSON).

I think it would be beneficial to add this because:

  • Native Compatibility: n8n is a JSON-based tool. The built-in storage should support the same data structures as the workflows themselves.
  • Workflow Simplicity: It eliminates the need for extra steps/expressions to stringify and parse data, making workflows cleaner and easier to maintain.
  • Data Integrity: It ensures that structured data is treated as such, rather than just text blobs.

Any resources to support this?

n8n Data Tables documentation: Data tables | n8n Docs
(Many modern databases support JSON/JSONB columns, e.g., PostgreSQL, which n8n often uses as a backend).

Are you willing to work on this?

The technical stack isn’t my area of expertise, but I would be happy to help with testing/debugging once it’s implemented.