Importing accounts: sessions, tdata and proxy binding
How to prepare your own sessions and proxies for import, review their state and avoid launching work before they are ready.
- Import only data you control
- Review the session and route
- Do not launch work on an error
Import connects your session, its metadata and the selected proxy. A file upload is not proof that an account is ready; confirm its state in the panel.
Prepare the data
- Use only sessions you are authorised to manage
- Keep original files in protected storage
- Confirm that the proxy is yours and reachable
Review the import
After upload, review the session status, proxy status and any validation error. Do not treat an account as ready when validation is incomplete, the session needs reauthorisation or the route is unavailable.
Next step
Before a job, choose an appropriate flow and review the validation outcome. Any Telegram action can lead to a restriction; the panel should show that as a fact, not hide it behind success.
FAQ
What data can I import?
Only panel-supported formats of sessions you control and their related metadata.
Can I launch a job immediately?
Only after confirming the session status and proxy binding. Validation errors need separate review.
What should I do with an invalid session?
Do not use it in a job. Review access and use an authorised reauthorisation flow when available.
Ready to open the panel?
Review the scenario constraints before launch.
