Telegram Trigger node receives messages but fails due to ‘No Access to Credential’ error

Describe the problem/error/question

I am experiencing an issue with the Telegram Trigger node in my workflow. The node correctly detects and receives messages from Telegram, but I receive the following error:

:pushpin: “Problem in node ‘Telegram Trigger’: Node has no access to credential.”

Despite this error, Telegram messages are received and processed, but the workflow does not proceed correctly beyond the trigger node.

What is the error message (if any)?

:pushpin: “Problem in node ‘Telegram Trigger’: Node has no access to credential.”

Share the output returned by the last node

Since the error occurs at the Telegram Trigger node, there is no output from subsequent nodes. However, Telegram messages are successfully received, but the workflow execution halts due to the credential error.

Information on your n8n setup

n8n version: 1.79.3

• **Database (default: SQLite)

Steps I Have Taken to Troubleshoot

  1. Credential Verification:

• Confirmed that my Telegram credential (“Final Tig API”) is set up correctly and tested successfully.

• Manually reselected the credential inside the Telegram Trigger node.

• Verified that my user has access to the credential in n8n’s settings.

  1. Webhook & Node Troubleshooting:

• Ensured that no other workflows are using the same Telegram bot webhook.

• Disabled and re-enabled the Telegram Trigger node.

• Switched the “Trigger On” setting from Message to another option and back.

  1. Credential Recreation:

• Deleted and recreated the Telegram credential.

• Ensured my bot’s API token is valid via BotFather.

Issue Behavior

The Telegram bot receives messages correctly (confirmed via Telegram UI).

The error appears immediately when a message is sent.

The workflow does not execute beyond the Telegram Trigger due to the credential error.

:pushpin: Has anyone else encountered this issue? Any ideas on how to fix it?

I’d really appreciate any guidance! :rocket:

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:

Hello @Gaisse

That error usually means that the workflow and the credential are in different Projects, so the workflow’s node is not able to access the specified credential.
Check the sharing tab of the credential

2 Likes

Yes, That was the issue…Thanks for your helpppp :rocket:

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