LINE WORKS Bot (Independent Publisher)

[iwaohig]

Proposal: LINE WORKS Bot API Connector

Overview

This pull request proposes a new Independent Publisher connector for LINE WORKS Bot API integration, providing
OAuth-based secure messaging capabilities for enterprise environments.

Key Differentiators

• OAuth 2.0 Authentication: Enterprise-grade security with proper access control
• Flexible Targeting: Send messages to any user or channel with Bot ID
• Phased Development: MVP text messaging with planned rich media expansion
• Enterprise Compliance: Full audit trail and secure token management

Complementary to Incoming Webhook

This Bot connector complements the existing LINE WORKS Incoming Webhook App proposal by addressing different use
cases:

• Incoming Webhook: Simple, no-auth notifications
• Bot Connector: Secure, authenticated enterprise messaging

Contact Information

• Publisher: iwaohig
• Email: [email protected]

Next Steps

Once approved as a proposal, I will implement the MVP version with OAuth authentication and basic text messaging
capabilities, followed by phased enhancements based on community feedback.

[certificationteam]

Hi @iwaohig,

Thank you for submitting the PR. You have submitted multiple PR proposals. Kindly keep the one PR and close all other PRs.

#3938

#3939

[iwaohig]

Hi @iwaohig,
Thank you for submitting the PR. You have submitted multiple PR proposals. Kindly keep the one PR and close all other PRs.
#3938
#3939

Thank you for reviewing our proposals. While both connectors are related to LINE WORKS, they serve different
purposes:

• LINE WORKS Incoming Webhook App (Independent Publisher) #3938 integrates with the Incoming Webhook App feature
• LINE WORKS Bot (Independent Publisher) #3939 integrates with the Bot API

These are fundamentally different integration methods with distinct use cases, authentication mechanisms, and
target audiences. Therefore, we would like to offer them as separate custom connectors.

Could you please clarify if it's possible to have both PRs reviewed independently? If not, we'd appreciate
guidance on the preferred approach - whether to:

1. Submit them sequentially (one after another)
2. Combine them into a single connector (though this may create complexity)
3. Choose one to proceed with first

Thank you for your guidance.

[troystaylor]

@iwaohig I have reviewed the Bot API and I would recommend that you combine the triggers with the actions. I do not believe there are too many actions for one connector, but also understand that you do not have to submit all actions in the API. Having one connector makes it easier for users to find all operations and it may make it easier for some organizations to approve the connector for use.

[iwaohig]

Hi @troystaylor and Microsoft team,

Thank you for your feedback. I understand the confusion caused by the naming, so let me clarify:

Regarding PR #3938 - "Incoming Webhook":
The term "Incoming" in "LINE WORKS Incoming Webhook App" refers to the perspective of the LINE WORKS chat room
(receiving incoming messages), not the connector's functionality. From Power Automate's perspective, this
connector only provides an action to send messages - it has no trigger capabilities.

Why these cannot be combined:

1. Different authentication models:
   - LINE WORKS Incoming Webhook App (Independent Publisher) #3938 (Webhook): No authentication required - uses webhook URL with embedded ID
   - LINE WORKS Bot (Independent Publisher) #3939 (Bot API): OAuth 2.0 authentication required
2. Different target users:
   - LINE WORKS Incoming Webhook App (Independent Publisher) #3938: Non-technical users who need simple notifications (just paste a webhook URL)
   - LINE WORKS Bot (Independent Publisher) #3939: Developers/IT teams who need secure, advanced messaging features
3. Different API endpoints:
   - LINE WORKS Incoming Webhook App (Independent Publisher) #3938: webhook.worksmobile.com (standalone webhook service)
   - LINE WORKS Bot (Independent Publisher) #3939: www.worksapis.com (main API platform)
4. Technical constraints:
   - Combining would force simple webhook users to configure OAuth (unnecessary complexity)
   - Or compromise security by making OAuth optional (not acceptable for enterprise Bot API)

Similar patterns in Power Platform:

• Slack has separate "Slack" (OAuth) and "Slack Webhook" (URL-only) connectors
• This separation serves the same purpose - simple vs. advanced use cases

Both connectors provide actions only (no triggers), serving different user needs. I kindly request these be
reviewed as separate connectors to maintain the appropriate simplicity/security balance for each use case.

Would you like me to clarify anything further?

[troystaylor]

@iwaohig, thank you for the clarification- I understand the use of the connectors now.

[iwaohig]

Complete Implementation Submitted

I have now submitted the complete implementation for the LINE WORKS Bot connector:

✅ Files Added

• apiDefinition.swagger.json - Full API definition with OAuth 2.0 authentication
• apiProperties.json - Connector properties and branding
• readme.md - Detailed setup instructions and documentation

🔧 Implementation Details

• Authentication: OAuth 2.0 with proper refresh token support
• Operations: Send text messages to users and channels
• Error Handling: Comprehensive HTTP status code responses
• Documentation: Complete setup guide with prerequisites

📋 Ready for Review

This connector is now ready for Microsoft certification review. The implementation follows all Independent
Publisher guidelines and provides a solid foundation for future enhancements (stickers, rich messages, etc.).

Thank you for your patience during the development process!