Hi n8n Team and Community,
Problem:
The Line Notify service, which allows sending notifications to Line, has announced the [end of its service / significant changes] (官方公告請見：LINE Notify). This deprecation means that any existing n8n workflows relying on Line Notify (whether through community nodes or potentially older methods) will cease to function correctly soon.
Line is a very popular messaging platform, especially in regions like Taiwan, Japan, and Thailand. The loss of this notification channel could impact a significant number of n8n users.
Proposed Solution:
I propose the development of a new, dedicated n8n node for Line integration, utilizing the official Line Messaging API. This API offers a much richer set of features compared to Line Notify, potentially allowing the node to support actions such as:
- Sending text messages to users, groups, or rooms.
- Sending images, videos, audio messages.
- Sending stickers.
- Sending rich message types (e.g., templates, flex messages).
- Potentially handling incoming messages/webhooks in the future (as a trigger node).
A dedicated node would provide a much better user experience and more robust integration compared to relying solely on the generic HTTP Request node.
Justification:
- Fills a Critical Gap: Provides a direct replacement for the deprecated Line Notify functionality, ensuring continuity for users.
- Addresses User Need: Caters to the large user base of Line, particularly in Asia.
- Enhances n8n Capabilities: Adds native support for a major communication platform.
Contribution Policy Acknowledgement:
I understand n8n’s contribution policy states that PRs for new nodes are generally auto-closed unless explicitly requested by the team and aligned with an agreed scope. Therefore, I am opening this issue first to:
- Bring this deprecation and the need for a replacement to your attention.
- Discuss the feasibility and desirability of adding an official Line Messaging API node to n8n’s core integrations.
- Gauge interest from the team and the community.
- Understand if this aligns with n8n’s current roadmap and priorities.
Next Steps & Offer:
Could the n8n team please share their perspective on this? Is official support for a Line Messaging API node something you would consider?
If this integration is deemed valuable and aligned with the project’s goals, I (and potentially others in the community) would be willing to contribute to its development and testing, following the team’s guidance and requirements.
Even if official inclusion isn’t feasible at this time, understanding the team’s stance would be helpful for those considering building it as a community/custom node.
Thank you for your time and consideration.