# Telegram Auto Buy

{% hint style="info" %}
Telegram Auto Buy runs Auto Buy inside a Telegram Web tab. When a contract address is posted in the channel you are watching, the Extension fires a buy automatically using your Scraper Preset.
{% endhint %}

***

### Requirements

Before starting Telegram Auto Buy, make sure:

* The Bloom Extension is **installed and signed in** (Solana, EVM, or both).
* Your **Scraper Preset** is configured at [manager.bloombot.app/extension/settings](https://manager.bloombot.app/extension/settings) > Scrapers tab. Set the Auto Buy Amount, fees, tip, slippage, and filters.
* You are using **Telegram K** (the K version of Telegram Web) in Chrome. Auto Buy does not work on Telegram A.
* Only **one Telegram tab** is open in the current browser window.

#### Switch to Telegram K

Telegram Web ships two versions (A and K). Bloom only supports K. Open `web.telegram.org/k/` directly in Chrome, or change the URL path from `/a/` to `/k/` if you are currently on the A version.

<div align="left"><figure><img src="https://3058400886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz2QdoaScujkQBx5Lf47O%2Fuploads%2FC75l9D5dRZGy82Ybmlzg%2Fk.png?alt=media&#x26;token=180fe73d-be49-4de9-bc4e-96d415c6eb9a" alt="" width="212"><figcaption></figcaption></figure></div>

***

### Starting Auto Buy

{% stepper %}
{% step %}
Open Telegram K in Chrome. Keep only one Telegram tab in the current browser window.
{% endstep %}

{% step %}
Navigate to the target channel and leave the tab active. The Extension injects a Bloom toolbar into the Telegram interface.
{% endstep %}

{% step %}
Verify your Scraper Preset in the Manager. Double-check the Auto Buy Amount, filters, and fees before going live.
{% endstep %}

{% step %}
Press the Auto Buy button injected into Telegram. Use <kbd>Start SOL Auto Buy</kbd> for Solana contracts, <kbd>Start EVM Auto Buy</kbd> for EVM contracts. You can run both at the same time if both Extensions are signed in.

<div align="left"><figure><img src="https://3058400886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz2QdoaScujkQBx5Lf47O%2Fuploads%2FSRqOvm7KmQd2UiC6Qsi2%2FSOL.png?alt=media&#x26;token=6a0d3d28-fe91-4937-bc8e-1cbb6a340b47" alt="" width="400"><figcaption><p>Solana</p></figcaption></figure></div>

<div align="left"><figure><img src="https://3058400886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz2QdoaScujkQBx5Lf47O%2Fuploads%2FclxQ8uvPF60Q9V9jivql%2FEVM.png?alt=media&#x26;token=b94351ee-a6c0-48ca-93c3-18e86de3f9eb" alt="" width="400"><figcaption><p>EVM</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

***

### What Happens Next

Once started, the Extension scans every new message in the active Telegram channel for contract addresses.

* **Address detected** → chain identified → Scraper Preset applied → buy fired.
* **Filter fails** (market cap, volume, or "previously bought") → buy skipped, scanning continues.
* **No address in the message** → ignored.

You can keep reading Telegram normally while Auto Buy runs. The Extension only reacts to contract addresses; regular messages and media are unaffected.

To stop Auto Buy, press the same button again (it toggles to <kbd>Stop Auto Buy</kbd>).

***

### Running Multiple Telegram Tabs

<details>

<summary>How do I monitor more than one Telegram channel at the same time?</summary>

Open each Telegram tab in a **separate browser window**. One window, one Telegram tab. Every window runs its own Auto Buy instance independently.

The limit is per window, not per browser profile, so you can open as many windows as your machine handles.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bloombot.app/extension/automation/telegram-auto-buy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.