ORD + Telegram Bridge
Diagnostic panel. Normal production flow is Gmail queue → ORD → ERID → Telegram.
Bridge key
ORD description
Approved ORD form
ORD type
Exact target URLs (optional; replaces defaults)
Extra target URLs (optional; appended to defaults)
KKTU codes (optional; defaults to configured code)
Allow approved form to differ from automatic media inference
Post text (without ERID)
Telegram schedule
Telegram channel
Media
Real job ID
I confirm ORD creation
Preflight (no ORD)
ORD readiness (READ-ONLY)
Dry-run to Telegram
REAL ORD + Telegram