Severity: priority/warning
Source: Internal UX audit (v0.7 sweep)
Area: packages/web, packages/runtime-node, packages/gateway
Problem
Configuring a gateway platform (Telegram bot, Slack app, Discord bot) requires:
- Creating a bot/app on the platform's portal
- Setting env vars
- Setting up the webhook URL
- Verifying with curl
This is documented somewhere but no in-dashboard wizard. /api/gateway/telegram/webhook returns 400 'token not configured' as the only feedback.
Proposed fix
- Connect/Gateway tab: one card per platform with status chip (Configured / Not configured / Errored).
- 'Configure' opens a 4-step wizard per platform:
- Step 1: External setup checklist with deeplinks ('Open BotFather', 'Open Slack app config', etc.).
- Step 2: Token input → server-side validation (
telegramGetMe etc.).
- Step 3: Public URL detection or input (with ngrok/cloudflared hint if localhost).
- Step 4: Auto-register webhook → poll status → success animation.
- Test message: after success, 'Send test message to your channel' button.
- Disconnect: cleanly removes webhook + clears token.
Expected impact
- Time-to-first-Telegram-message drops from 'unclear, ask in Discord' to <5 minutes.
- Drives platform adoption beyond the dashboard.
- Reduces 'why isn't my bot responding?' triage to a green/red status check.
References
- Internal v0.7 platform polish audit
Severity: priority/warning
Source: Internal UX audit (v0.7 sweep)
Area:
packages/web,packages/runtime-node,packages/gatewayProblem
Configuring a gateway platform (Telegram bot, Slack app, Discord bot) requires:
This is documented somewhere but no in-dashboard wizard.
/api/gateway/telegram/webhookreturns 400 'token not configured' as the only feedback.Proposed fix
telegramGetMeetc.).Expected impact
References