# \[APPROVED\] New Field Type: JSON **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [October 13, 2025, 11:56am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816 "2025-10-13T11:56:09Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![DominikM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dominikm/32/13689_2.png) [@DominikM](https://community.fibery.io/u/DominikM)\ **Post date:** [October 13, 2025, 11:56am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/1 "2025-10-13T11:56:09Z")
would like to pass the “speakers” from fireflies (like e-mails) as json (array) to fibery and then run some automations (with rules), as example: to identify the fibery users which are existing for this e-mails and link them to a multi select field in fibery. The use case in most parts is to have automations working with the json data and enrich fibery datasets with it 🙂 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 13, 2025, 12:05pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/2 "2025-10-13T12:05:33Z")
We’ll think about making JSON a proper field ---
**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\ **Post date:** [October 13, 2025, 4:43pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/3 "2025-10-13T16:43:34Z")
Added support for json fields. Should be available starting from 0.1.8 node’s version ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [October 13, 2025, 11:19pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/4 "2025-10-13T23:19:47Z")
I love JSON. Don’t know how it’ll be used, but I’d find a way! ```auto { "people": [ { "name": "Derulo" }, { "name": "Statham" }, { "name": "Moama" } ] } ``` ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [October 15, 2025, 10:35am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/5 "2025-10-15T10:35:05Z")
@AdVhPkgKad @DominikM as somebody who has heavily used pseudo-JSON fields in Podio (Formula fields using javascript JSON.stringify and JSON.decode to convert hidden text fields into JSON) for over a decade, I have a question for you: **In Fibery, since its formulas do not use javascript, would JSON fields not be limited to use in automations only**? I ask, because in Podio, formula/calculation fields use javascript (though the outdated ES5), which gives immense power to JSON fields, for example we encode records otherwise not able to be looked up without tens of extra intermediary fields, and pass them on across multi-hop relationships to be used in related records in other tables/databases/apps. That said, many of these things can be done in Fibery without the need for my old hacks 🥳, though of course I would love javascript inside the formula fields! ---
**Author:** ![Bachi2k](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bachi2k/32/1770_2.png) [@Bachi2k](https://community.fibery.io/u/Bachi2k)\ **Post date:** [October 15, 2025, 11:20am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/6 "2025-10-15T11:20:28Z")
@Sev We also used this Method in Podio back in the day, before we noticed, that Fibery is a better option. In my new Company, we startet from scratch with Fibery. Currently we do not see this need for a JSON field in Fibery, since the Relationships are also way better than in Podio and the API gives us the needed freedom for all the rest. So Hi to another old Podio Poweruser! 😄 ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [October 15, 2025, 12:27pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/7 "2025-10-15T12:27:45Z")
Would be cool if the JSON field could also be used for GeoJSON, then you can easily put it on the map as points, lines and polygons. See: > **[geojson.io | powered by Mapbox](https://geojson.io/#map=6.15/51.96/7.071)** > > A quick, simple tool for creating, viewing, and sharing spatial data. (draw some features using the menu on the top-right of the map, see how the geojson looks) ---
**Author:** ![Finanzamt\_Muellheim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/finanzamt_muellheim/32/12892_2.png) [@Finanzamt\_Muellheim](https://community.fibery.io/u/Finanzamt_Muellheim)\ **Post date:** [October 15, 2025, 2:01pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/8 "2025-10-15T14:01:11Z")
I would love the GeoJSON, could make things faster for the maps that I created 😁 the Latitude and Longitude can’t plot my point on the Map View ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [October 20, 2025, 10:23am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/9 "2025-10-20T10:23:21Z")
Hello @Bachi2k! nice to meet you, too. I agree 100%. We are also remodelling the data fully before importing it into Fibery, though I must say I miss the markdown display, and of course JS inside formulas! Thankfully, for you it is in the past, but we are still in the process of migrating. Remember the maximum depth of 10 calculations?! Haha. ---
**Author:** ![Wilco\_Boode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/wilco_boode/32/9985_2.png) [@Wilco\_Boode](https://community.fibery.io/u/Wilco_Boode)\ **Post date:** [October 20, 2025, 11:43am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/10 "2025-10-20T11:43:04Z")
Awesome, we use Json a lot and this can help with config files etc. I vouch for the GeoJson request. Its amazing for our data-visualizations. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 20, 2025, 1:52pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/11 "2025-10-20T13:52:52Z")
Related / the same: > [@Request: new field type 'Code' (not rich text field with code block in it)](https://community.fibery.io/t/request-new-field-type-code-not-rich-text-field-with-code-block-in-it/8757): > > I like to suggest the creation of a new field of type ‘Code’ Reason: Using a rich text document field always requires to include manually (or automatic) insertion of a code block (backticks) to store code. This is overcomplication when working with automations and workflows that handle code and not rich text. A dedicated ‘Code’ field offers: Clear, direct programmatic access to raw code, unlike the need to parse formatted text in rich text. Structured storage of code language, enabling lang… ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [October 20, 2025, 2:14pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/12 "2025-10-20T14:14:37Z")
Have you created a feature request? 😉 ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [October 20, 2025, 2:17pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/13 "2025-10-20T14:17:15Z")
Haha I think I try to self-limit my map propaganda! 😁 (my strategy now is to try to get in a few dozen customers and encourage them to ask about maps 😄) ((do not worry I will build in the map features I may need myself in some way for my customers via the API and outside scripts/applications 😛 I want Fibery to stay good in the main thing they do that is the core for all and not distract them. But if I notice patterns in my customers need and if I have ideas on smart & easy map features (in my estimation) that really add value then I will do a feature request. )) ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [October 20, 2025, 2:33pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/14 "2025-10-20T14:33:05Z")
Why not just focusing on the clients that need maps in the daily work without the need to encouraging them? (let’s keep our convo off this topic) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 27, 2025, 12:05pm UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/15 "2025-10-27T12:05:49Z")
2 posts were split to a new topic: [New Field: Code](https://community.fibery.io/t/new-field-code/9893) ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [September 11, 2026, 2:13am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/16 "2026-09-11T02:13:36Z")
Bump Just thought that since the introduction of custom apps, having a JSON field could store: - Configuration settings for those apps against user accounts - Canvas items (location, rotation, colour, shape) - Complex relationships for use in apps, without creating new tightly-coupled databases Also, theoretically, you could run Doom on Fibery (I do not condone this). ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [September 11, 2026, 7:06am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/17 "2026-09-11T07:06:04Z")
It’s actually possible already. Hold Option/Alt when you create a new field, and you’ll have JSON as an option. Recently they also added the UI for it in the entity view. Note that AI doesn’t know it can create proper JSON fields, but after you create it, it can use them within Custom Apps for some of the use cases you described. It’s pretty cool! Those JSON fields have lots of potential ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 11, 2026, 8:37am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816/18 "2026-09-11T08:37:01Z")
I hope we will add it properly in near future