channels_connect_session_submit
Hand a connect session what the person typed: exactly ONE of phone, code, password.
need_phone →
phone(international format). WhatsApp answers need_pairing_code with the 8-characterpairing_codeto type on the phone; Telegram sends a code and answers need_code.need_code →
code(Telegram). Answers connected, or need_password when the account has two-step verification.need_password →
password(Telegram two-step verification).
A mistyped code or password is refused with error_type validation and the session stays where it is: submit again. 10 submits per session, then rate_limited and the session ends. Nothing submitted here is logged or stored after the session ends.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"session_id": "<session_id>"
},
"name": "channels_connect_session_submit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | The sign-in code Telegram sent. Only at need_code. | |
| phone | No | The phone number, e.g. +380501234567. Only at need_phone. | |
| password | No | The Telegram two-step verification password. Only at need_password. | |
| session_id | Yes | The session_id that channels.connect_session.start returned. | |
| in_workspace | No | Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected. |