ChatGPT Telegram bot - messages do not thigger the workflow

Questions
1

The workflow should be triggered by the messages from the telegram bot. But in 80% cases messages sent to the telegram bot do not trigger the workflow execution. Obly if I press the Test Workflow button then it triggers and the workflow executes.

image
image456Ă—745 28.7 KB

image
image854Ă—406 30.9 KB

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

Hi @Anton_D

Thanks for posting here and welcome to the community! :tada:

I wonder if this is because you have set to trigger on Message and *
Is there any particular reason you’re doing that?
If you want the bot to trigger on everything, the * asterisk only should suffice.

Haven’t been able to test this yet - but please let us know if it makes a difference.

Also, how did you check whether a message / update didn’t trigger the bot? Did you check the executions for any errored ones?

1 Like
4

Neither trigger Message or * or both of them work. I tried all combinations.
How did I check:

  • With “*” + “message” triggers OR with only “message” trigger:
    Our team sent messages to the telegram bot from multiple telegram account. There were no execution records in the workflow. But after pressing Test Workflow all the messages sent to the bot triggered and workflow executed correctly. It loks likes it wasn’t listening untill I pressed the Test button.
  • With “*” trigger: the error apears only at the last step. “Bad Request: can’t parse entities: Can’t find end of the entity starting at byte offset 2785”
    {
    “errorMessage”: “Bad request - please check your parameters”,
    “errorDescription”: “Bad Request: can’t parse entities: Can’t find end of the entity starting at byte offset 2785”,
    “errorDetails”: {
    “rawErrorMessage”: [
    “400 - {"ok":false,"error_code":400,"description":"Bad Request: can’t parse entities: Can’t find end of the entity starting at byte offset 2785"}”
    ],
    “httpCode”: “400”
    },
    “n8nDetails”: {
    “nodeName”: “Telegram”,
    “nodeType”: “n8n-nodes-base.telegram”,
    “nodeVersion”: 1.2,
    “resource”: “message”,
    “operation”: “sendMessage”,
    “time”: “9/5/2024, 5:17:32 PM”,
    “n8nVersion”: “1.56.2 (Cloud)”,
    “binaryDataMode”: “filesystem”,
    “stackTrace”: [
    “NodeApiError: Bad request - please check your parameters”,
    " at Object.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/GenericFunctions.js:115:15)“,
    " at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
    " at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/Telegram.node.js:1763:36)“,
    " at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:728:19)”,
    " at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:673:51",
    " at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1104:20"
    ]
    }
    }
    image
    image593Ă—538 20.9 KB