# Agent Builder — Customizing Tool Approval Message Content **URL:** \ **Category:** Questions\ **Tags:** telegram, bug:unconfirmed\ **Created:** [October 12, 2026, 6:57pm UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987 "2026-10-12T18:57:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Wildflower\_Studio](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wildflower_studio/32/191665_2.png) [@Wildflower\_Studio](https://community.n8n.io/u/Wildflower_Studio)\ **Post date:** [October 12, 2026, 6:57pm UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987/1 "2026-10-12T18:57:54Z")
Hi n8n community, I’m using the **Agent Builder** (not the AI Agent workflow node) and have tools connected to my agent that require approval before executing. When the agent asks for approval, the message only shows **which tool** it’s going to execute, but not **what it’s actually going to change** (e.g., the specific parameters or values the tool will use). **What I’d like:** A way to customize the approval message in the Agent Builder so it shows more context — specifically the parameters/values the tool is about to use — so I can make an informed decision before approving or rejecting. **Questions:** 1. Is there currently a way to customize the approval message content in the Agent Builder? 2. If not, is this something that could be added as a feature? Thanks! ---
**Author:** ![Deepankar](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/deepankar/32/197564_2.png) [@Deepankar](https://community.n8n.io/u/Deepankar)\ **Post date:** [October 12, 2026, 7:06pm UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987/2 "2026-10-12T19:06:03Z")
Hey @Wildflower_Studio Welcome in to the N8n community, Not the message text itself. It’s fixed (“The agent wants to run the X tool.”), and the per-tool approval setting is only an on/off switch. What the card can show is the call’s arguments, and that part has just changed. On the current stable 2.42, the details box on the approval card in the Agent Builder chat only holds what the model passed into the tool, so a tool whose fields are set in its config shows little more than its name. In 2.43, which is on the beta track right now, the card for a node-based tool shows the node’s configured parameters with the model’s values filled in, plus the raw input, so you can see what it’s about to change before you approve. That release also adds an “Allow for this session” option. Approvals that go out through Slack, Telegram or Linear still show only the tool name, even in 2.43, so that part would need a feature request. ---
**Author:** ![Wildflower\_Studio](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wildflower_studio/32/191665_2.png) [@Wildflower\_Studio](https://community.n8n.io/u/Wildflower_Studio)\ **Post date:** [October 16, 2026, 7:52am UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987/3 "2026-10-16T07:52:36Z")
So I reckon I’d have to raise a feature request then? ![image](https://europe1.discourse-cdn.com/n8n/original/3X/7/0/70254988d421d4e478764106797ec94c1e5dbc61.png) As you can see, the arguments aren’t displayed as well, in the Telegram bot chat itself. ---
**Author:** ![HomelabAgent](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@HomelabAgent](https://community.n8n.io/u/HomelabAgent)\ **Post date:** [October 16, 2026, 2:08pm UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987/4 "2026-10-16T14:08:20Z")
The approval card text is fixed, so a feature request is the right track, but you don’t have to wait for it: make the approval itself a tool the agent calls. A sub-workflow exposed as a Call n8n Workflow Tool takes the proposed parameters as its own arguments, sends them to you with the Telegram node’s **Send and Wait for Response** (approval) operation in a message template you control, and returns approved/denied to the agent. Because the message is your node, you get the exact values in the text, and you can render them as readable key/value lines with a Code node instead of raw JSON. The tradeoff is that it depends on the model calling the tool at the right moment, so keep the built-in per-tool approval on as a backstop and state in the agent’s system prompt that it must call the approval tool before any write tool. ---
**Author:** ![Marchik](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/marchik/32/168873_2.png) [@Marchik](https://community.n8n.io/u/Marchik)\ **Post date:** [October 17, 2026, 2:01pm UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987/5 "2026-10-17T14:01:05Z")
@Wildflower_Studio Your screenshot shows `Airtable_WRITE_revert_action`, but not which record or values it will change. If you try the workflow workaround, I’d keep the approval and the actual write inside the same tool. A separate approval tool returning `approved: true` to the agent doesn’t establish that its next tool call will use the values you approved. For Agent Builder, that means exposing a workflow as the action tool. It would be a custom approval flow, not a way to change the existing Telegram card. Inside that workflow, I’d use this sequence: 1. Validate the proposed action and save a fixed copy under a request ID. 2. Build the Telegram message from that copy: the action, the target record ID and the field values that will change. Keep the approval destination configured by the workflow, rather than supplied by the model. 3. Use **Send and Wait for Response** with the Approval response type. Set a wait limit and continue to the write only on an explicit approval; denial or expiry must end that path. 4. Apply the saved values and return the result to the agent. Don’t leave a separate, unguarded version of the same write tool available to it. If someone changes the proposed values, require a new approval. Test on your n8n version with dummy data first: approve an update to A, confirm that only the displayed changes reach A, and check that the agent receives the result after the wait. Then try to use that approval for B: B should remain untouched. Declining or letting the request expire should cause no write. What inputs does that Airtable action accept? Those are the values I’d map into the approval message. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [October 24, 2026, 2:01pm UTC](https://community.n8n.io/t/agent-builder-customizing-tool-approval-message-content/320987/6 "2026-10-24T14:01:41Z")
Closed on October 24, 2026, 2:01pm UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.