# Baserow n8n Node Lacks Flexibility with Field Names (Only Supports Field IDs)
**URL:** https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397
**Category:** Technical Help
**Tags:** automation, template, n8n
**Created:** [October 26, 2025, 4:22am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397 "2025-10-26T04:22:26Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@dangngocbinh](https://community.baserow.io/u/dangngocbinh)
#### Post date: [October 26, 2025, 4:22am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/1 "2025-10-26T04:22:26Z")
### Are you using our SaaS platform ([Baserow.io](http://Baserow.io)) or self-hosting Baserow?
SaaS
### What are the exact steps to reproduce this issue?
First, thank you to the Baserow team for building such an amazing open-source platform. The new Application Builder is fantastic — it empowers No Code users to quickly create user-friendly apps.
I’ve built a workflow using n8n and Baserow that works perfectly. However, sharing it with others is difficult because each user’s database, table, and field IDs are different, causing the workflow to fail. Reconnecting fields manually is time-consuming and error-prone.
Since Baserow uses fixed field IDs, it’s hard to share n8n workflows. Other platforms like Notion or Airtable allow workflows to run even after duplicating databases, thanks to flexible field name handling.
I hope Baserow will improve the n8n Node to support field names, making it easier for everyone to use and share n8n workflows with Baserow.
Thanks again for your great work!
### Attach screenshots, videos, or logs that demonstrate the issue.
---
### Author:  [@olgatrykush](https://community.baserow.io/u/olgatrykush)
#### Post date: [October 28, 2025, 2:48pm UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/2 "2025-10-28T14:48:22Z")
Hello @dangngocbinh, we’ve actually been working on updating the n8n integration recently, but unfortunately, this wasn’t one of the changes. So, I’ve created this issue to track and fix it: [Support using field names instead of field IDs in n8n integration · Issue #4129 · baserow/baserow · GitHub](https://github.com/baserow/baserow/issues/4129) 🙂
---
### Author:  [@dangngocbinh](https://community.baserow.io/u/dangngocbinh)
#### Post date: [October 29, 2025, 5:32am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/3 "2025-10-29T05:32:03Z")
Thank you @olgatrykush for your quick response! I’m glad to hear the team is working on updating the n8n integration.
May I take a look at the source code for this feature and help contribute to the update if I can? I would love to participate and help improve this feature for the community.
Thank you so much to the team! 🙏
---
### Author:  [@olgatrykush](https://community.baserow.io/u/olgatrykush)
#### Post date: [October 29, 2025, 9:34am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/4 "2025-10-29T09:34:53Z")
I think so! Let me check with the team and I’ll get back to you on this 🙌
---
### Author:  [@olgatrykush](https://community.baserow.io/u/olgatrykush)
#### Post date: [October 29, 2025, 4:14pm UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/5 "2025-10-29T16:14:08Z")
Hey @dangngocbinh, I just checked with the team — we’d really appreciate it if you could contribute this feature yourself!
We just ask that you wait until the latest changes we’ve made are merged, so you can work with the updated node: [https://github.com/n8n-io/n8n/pull/19758](https://github.com/n8n-io/n8n/pull/19758)
The source code is open in the n8n repository here:
[https://github.com/n8n-io/n8n/tre](https://github.com/n8n-io/n8n/tree/master/packages/nodes-base/nodes/Baserow)
---
### Author:  [@dangngocbinh](https://community.baserow.io/u/dangngocbinh)
#### Post date: [October 31, 2025, 5:55am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/6 "2025-10-31T05:55:22Z")
Thank you! I’ll wait.
In the meantime, I’ll take a look at how n8n nodes are written to figure things out.
I believe the node will fetch the database table schema and automatically map the field names to IDs when executed.
Please let me know once the merge is complete so I can get started.
Kind regards
---
### Author:  [@Mary-Lou](https://community.baserow.io/u/Mary-Lou)
#### Post date: [July 24, 2026, 10:43am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/7 "2026-07-24T10:43:10Z")
Any updates on this? 🙂
---
### Author:  [@olgatrykush](https://community.baserow.io/u/olgatrykush)
#### Post date: [July 28, 2026, 9:13am UTC](https://community.baserow.io/t/baserow-n8n-node-lacks-flexibility-with-field-names-only-supports-field-ids/11397/8 "2026-07-28T09:13:18Z")
Hey @Mary-Lou, if that’s what you’re asking about, the Baserow node in n8n was updated back in 2025.