Why does disabling n8n attribution on my trial account cause a Telegram node error?

Based on the available documentation, there isn’t any indication that trial accounts affect the behavior of the n8n Telegram node when disabling the attribution. The attribution toggle is designed to work independently of your account status. The docs simply outline how to disable the attribution by turning off the Append n8n attribution option.

If you’re encountering an error when disabling the attribution on your trial account, it might be due to another configuration or a bug. Here are a few suggestions:

1. Double-check your configuration: Ensure that you followed the steps as documented for removing the attribution.
2. Inspect the error message: Look for any details in the error output that could help pinpoint the issue (e.g., missing parameters or misconfigurations).
3. Compare environments: Since it works with the attribution enabled, try testing in a different environment (if possible) to rule out any trial-specific issues.
4. Reach out to Support/Community: If the issue persists, consider opening an issue on the n8n community forum or GitHub repository. This can help determine if it’s an isolated problem or a known bug.

No known reports link this behavior specifically to trial account status. Let us know if you find further details while troubleshooting!