Skip to content

Telegram Bot Setup

Liviu Stoica edited this page May 20, 2026 · 1 revision

Telegram Bot Setup

The Server Edition includes a Telegram bot that allows authorized users to sign documents remotely — from any device, without opening XignAll.


How it works

  1. Authorized user sends a file (or photo) to the bot in Telegram
  2. XignAll receives the file on the server
  3. Converts to PDF if needed
  4. Signs with the configured SEAL profile
  5. Sends the signed PDF back — typically within seconds

Supported input

Type Formats
Office documents .docx, .doc, .odt, .rtf, .txt, .xlsx, .xls, .ods, .csv
Images .jpg, .jpeg, .png, .bmp, .tiff, .gif, .webp
Phone camera photo Supported — Telegram sends as compressed JPG
PDF Signed directly, no conversion

Setup

Step 1 — Create a Telegram bot

  1. Open Telegram → search for @BotFather
  2. Send /newbot
  3. Choose a name (e.g. XignAll Signing) and a username (e.g. xignall_sign_bot)
  4. Copy the API token provided by BotFather

Step 2 — Configure in XignAll

  1. Open XignAll → Server tab → Telegram
  2. Paste the API token
  3. Set the SEAL profile to use for signing
  4. Add authorized user IDs (see below)
  5. Click Start bot

Step 3 — Find your Telegram user ID

Send a message to @userinfobot on Telegram — it replies with your numeric user ID (e.g. 123456789). Add this ID to the authorized users list in XignAll.


Access control

Only users whose numeric Telegram ID is in the authorized list can use the bot. All other messages are ignored silently.

Admin commands (available to the account that started the bot):

Command Description
/status Show bot status and SEAL profile
/users List authorized users
/log Show last 20 journal entries

Example use case

A notary is away from the office. A colleague photographs a document and sends it to the bot from their phone. Within seconds they receive a SEAL-signed PDF — without accessing a computer, without a VPN, and without any document leaving the organization's server.


Notes

  • The bot requires an internet connection on the server running XignAll (to connect to Telegram's API)
  • Documents are processed locally — Telegram only transmits the file, XignAll does not use any Telegram cloud storage
  • Multiple instances detection: if two XignAll instances are configured with the same bot token, the conflict is detected and reported
  • LibreOffice must be installed on the server for non-PDF input conversion

Clone this wiki locally