Need Assistance with Optimizing Chatbot Workflow in n8n

Questions
1

Hi everyone,

I hope you’re doing well! I’m currently working on a project to optimize a chatbot workflow in n8n , and I could really use your expertise. Here’s the situation:

  1. Objective:
  • I’m building a chatbot that collects user input, processes it through multiple agents, and sends the final data to Bitrix24 via API.
  1. Current Challenge:
  • When using the “Send and wait for response” operation in the Telegram node, an automatic message (“This message was sent automatically with n8n”) is being appended to the response.
  • I tried disabling attribution globally using the N8N_APPEND_ATTRIBUTION=false environment variable, but it didn’t work for this specific operation.
  • The operation doesn’t have an option to disable attribution in the node settings.
  1. What I Need Help With:
  • Is there a way to completely remove the automatic attribution message for the “Send and wait for response” operation?
  • Alternatively, is there a workaround (e.g., using a custom node, API call, or another method) to achieve this?
  1. Additional Context:
  • I’m using a self-hosted instance of n8n on Render.com.
  • The chatbot workflow involves multiple agents, and this issue is affecting the user experience.
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hey!

Can you please share a screenshot of node that is generating this message?

4

Hey @Gepsyz8,
Since the N8N_APPEND_ATTRIBUTION=false environment variable isn’t working for this specific case, I’ve put together a workaround that involves modifying the Telegram node’s source code in n8n.

To ensure clarity, I’ve documented the entire process in a step-by-step guide, including a warning to back up your instance before making any changes. You can access the document here: Manually Remove the Attribution from Telegram.node.js.docx - Google Docs

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.