Bug Description
When using a node with usableAsTool: true as a tool in an AI Agent workflow, fields with the parameter name name do not show the "✦ Defined automatically by the model" ($fromAI) button, while all other string fields with identical configuration do.
This prevents AI agents from dynamically generating titles/names for resources, which is a common requirement for content management nodes.
I discovered this while working on the n8n-nodes-bookstack community node. To isolate the issue, I added multiple test fields with identical configuration — the only difference being the parameter name:
| Field |
Parameter name |
$fromAI button |
| Page Title (AI) |
page_title |
✅ appears |
| Test Name Field |
test_name_field |
✅ appears |
| Name |
name |
❌ missing |
| Book ID |
book_id |
✅ appears |
| Chapter ID |
chapter_id |
✅ appears |
| Markdown Content |
markdown |
✅ appears |
| Tags |
tags |
✅ appears |
All fields use type: 'string', no required: true, same displayOptions. The name field is the only one excluded.
This appears to be the same root cause as #16793 (Supabase Vector Store), which was closed as stale.
Workaround: Add a second field with a different parameter name (e.g. page_title) and map it to name internally before the API call. This works but results in two fields for the same purpose.


To Reproduce
- Install or create any community node with
usableAsTool: true
- Define two fields in the node's description with identical config:
- Field A:
{ displayName: 'Name', name: 'name', type: 'string', default: '' }
- Field B:
{ displayName: 'Title', name: 'title', type: 'string', default: '' }
- Create a new workflow with an AI Agent node
- Click "+" on the Agent's Tools slot and add the custom node as a tool
- Open the tool node's Parameters tab
- Observe: "Title" has the ✦ ($fromAI) button, "Name" does not
Expected behavior
All string fields should show the "✦ Defined automatically by the model" ($fromAI) button in AI Agent tool mode, regardless of their parameter name. The parameter name name should not be treated differently from any other parameter name.
Debug Info
...
Operating System
Windows 11 (Docker Desktop)
n8n Version
2.15.0
Node.js Version
20
Database
SQLite (default)
Execution mode
main (default)
Hosting
self hosted
Bug Description
When using a node with
usableAsTool: trueas a tool in an AI Agent workflow, fields with the parameter namenamedo not show the "✦ Defined automatically by the model" ($fromAI) button, while all other string fields with identical configuration do.This prevents AI agents from dynamically generating titles/names for resources, which is a common requirement for content management nodes.
I discovered this while working on the n8n-nodes-bookstack community node. To isolate the issue, I added multiple test fields with identical configuration — the only difference being the parameter name:
page_titletest_name_fieldnamebook_idchapter_idmarkdowntagsAll fields use
type: 'string', norequired: true, samedisplayOptions. Thenamefield is the only one excluded.This appears to be the same root cause as #16793 (Supabase Vector Store), which was closed as stale.
Workaround: Add a second field with a different parameter name (e.g.
page_title) and map it tonameinternally before the API call. This works but results in two fields for the same purpose.To Reproduce
usableAsTool: true{ displayName: 'Name', name: 'name', type: 'string', default: '' }{ displayName: 'Title', name: 'title', type: 'string', default: '' }Expected behavior
All string fields should show the "✦ Defined automatically by the model" ($fromAI) button in AI Agent tool mode, regardless of their parameter name. The parameter name
nameshould not be treated differently from any other parameter name.Debug Info
...
Operating System
Windows 11 (Docker Desktop)
n8n Version
2.15.0
Node.js Version
20
Database
SQLite (default)
Execution mode
main (default)
Hosting
self hosted