Choose Platform Integration
Purpose
Choose the real platform surface before code, credentials, or a shared abstraction are added. The result is a documented integration shape and one implementation handoff, not a fictional universal bot SDK.
Workflow
- Classify the request as a server bot, workspace app, business messaging agent, meeting add-on, native Messages extension, VoIP calling app, or Mac operator workflow.
- Identify the user, installation, identity, inbound-event, outbound-response, and hosting model.
- Check current official platform docs for availability, policy, review, consent, and SDK lifecycle.
- Select the owning platform workflow and then the owning stack workflow.
- Define the minimum secure event contract before implementation: verified source, acknowledgement deadline, idempotency key, retry behavior, state owner, audit boundary, and human handoff.
Routing
- Discord: installed app and HTTP/Gateway interactions; use
discord-app-workflow.
- Telegram: Bot API, webhook or polling, optional Mini App; use
telegram-bot-workflow.
- Slack: workspace OAuth app, Events API, interactivity, or Socket Mode; use
slack-app-workflow.
- Teams: Teams SDK or Microsoft 365 Agents SDK; use
teams-agent-workflow.
- WhatsApp, SMS, MMS, or RCS: business-messaging route; use
whatsapp-business-workflow or sms-mms-rcs-workflow.
- Google Meet: add-on, REST conference/artifact integration, or explicitly preview media access; use
google-meet-collaboration-workflow.
- Apple: iMessage/Shared with You, communication notifications, Push to Talk, CallKit/LiveCommunicationKit plus PushKit/AVFAudio, documented iOS/iPadOS default roles, or an app-owned macOS client; use
apple-communication-workflow.
- Signal: report that no official bot route is supported; do not substitute account automation.
Output
Return the selected surface, reasons, documented constraints, credential and data boundary, implementation owner, validation plan, and rejected alternatives. Stop if the requested platform capability is unsupported or needs a product-policy decision.
1---2name: choose-platform-integration3description: Choose a supported chat, calling, business-messaging, or collaboration integration before implementation. Use for Discord, Telegram, Slack, Teams, WhatsApp Business, SMS/MMS/RCS, Google Meet, iMessage collaboration, and Apple VoIP.4---56# Choose Platform Integration78## Purpose910Choose the real platform surface before code, credentials, or a shared abstraction are added. The result is a documented integration shape and one implementation handoff, not a fictional universal bot SDK.1112## Workflow13141. Classify the request as a server bot, workspace app, business messaging agent, meeting add-on, native Messages extension, VoIP calling app, or Mac operator workflow.152. Identify the user, installation, identity, inbound-event, outbound-response, and hosting model.163. Check current official platform docs for availability, policy, review, consent, and SDK lifecycle.174. Select the owning platform workflow and then the owning stack workflow.185. Define the minimum secure event contract before implementation: verified source, acknowledgement deadline, idempotency key, retry behavior, state owner, audit boundary, and human handoff.1920## Routing2122- Discord: installed app and HTTP/Gateway interactions; use `discord-app-workflow`.23- Telegram: Bot API, webhook or polling, optional Mini App; use `telegram-bot-workflow`.24- Slack: workspace OAuth app, Events API, interactivity, or Socket Mode; use `slack-app-workflow`.25- Teams: Teams SDK or Microsoft 365 Agents SDK; use `teams-agent-workflow`.26- WhatsApp, SMS, MMS, or RCS: business-messaging route; use `whatsapp-business-workflow` or `sms-mms-rcs-workflow`.27- Google Meet: add-on, REST conference/artifact integration, or explicitly preview media access; use `google-meet-collaboration-workflow`.28- Apple: iMessage/Shared with You, communication notifications, Push to Talk, CallKit/LiveCommunicationKit plus PushKit/AVFAudio, documented iOS/iPadOS default roles, or an app-owned macOS client; use `apple-communication-workflow`.29- Signal: report that no official bot route is supported; do not substitute account automation.3031## Output3233Return the selected surface, reasons, documented constraints, credential and data boundary, implementation owner, validation plan, and rejected alternatives. Stop if the requested platform capability is unsupported or needs a product-policy decision.
gaelic-ghost