> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/telegram-and-promotion/28-buybot-setup.md).

# 28. Set up the Telegram Buy Bot

Connect a supported token to a project group, preview alerts and diagnose missing buys.

**Open:** [Buy Bot setup](https://spawnmeme.com/trending#buybot). The Buy Bot publishes supported, confirmed buy activity into a Telegram community; it does not buy tokens for members.

## Requirements

* A verified SPAWN token on an **active supported bonding curve**.
* A Telegram group you administer from a visible personal admin account.
* [@spawnmeme\_bot](https://t.me/spawnmeme_bot) added as a group administrator with the required posting/media permissions.
* Available platform monitoring capacity and enabled creator connections.

Graduated pools and arbitrary external Solana tokens are not currently supported. Connecting a token to a group does not prove that the group owns or officially represents that token.

## Connect and preview

1. Choose the token on the setup page, or paste its full mint.
2. Add the official bot to your project group and promote it to administrator.
3. From your visible group-admin account, send:

```
/buybot YOUR_TOKEN_MINT
```

4. Check the connected-token confirmation and `/ca` response.
5. Open settings and post a labelled test:

```
/buybotsettings
/buybotpreview 0.5
```

6. Confirm that the sample displays the intended token, media and buttons.

Replace `YOUR_TOKEN_MINT` with the real address. The preview is synthetic: it does not buy, change rankings or count as payment. Configuration and previews require a visible administrator, not an anonymous admin/channel identity.

## Alert information

| Field                      | Interpretation                                                       |
| -------------------------- | -------------------------------------------------------------------- |
| Buy amount and transaction | Supported confirmed activity; use the transaction link to inspect it |
| Market cap (est.)          | Pool-price and supply estimate, not exit liquidity                   |
| Bonding curve              | Progress against this token's configured migration threshold         |
| Holders                    | Indexed data when available; absence is not zero                     |
| USD value                  | Optional approximate SOL conversion                                  |
| Buyer badge                | Only shown when supported by verified history/evidence               |
| Trending rank              | Current qualifying organic activity rank                             |
| Promoted badge             | Separately purchased sponsored visibility                            |

One token is connected per group. Several groups can follow the same supported token subject to capacity. The main SPAWN group retains its official configuration.

## Pause or resume

Use `/stopbuybot` to pause alerts and `/resumebuybot` to resume. Use `/buybotsettings` to inspect the group's minimum buy amount and display options. Settings apply to that group.

## Troubleshooting

| Symptom                               | Resolution                                                                                                                                      |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Not an admin / cannot verify admin    | Use a visible group-admin account and confirm both your role and the bot's role.                                                                |
| Unsupported token                     | Check full mint, verified SPAWN registration and active curve state.                                                                            |
| Capacity reached / activation pending | Wait for capacity or activation; paying for promotion does not bypass support limits.                                                           |
| Sample works, real buy missing        | Check confirmation, alert minimum, pause state and supported pool. Allow indexing/monitoring time.                                              |
| Media alerts fail                     | Verify Telegram posting/media permissions and [media limits](/spawnmeme-docs/feature-guides/telegram-and-promotion/29-buybot-customization.md). |
| Market cap or curve unavailable       | Data could not be read/verified for that alert. Recheck the token page and report persistent errors with mint and signature.                    |
| Holder count unavailable              | Provider indexing may lag; it is not evidence of zero holders.                                                                                  |
| Buy appeared once but not again       | Delivery avoids duplicate announcements; a missing duplicate is not necessarily a fault.                                                        |

Buy alerts are free for supported tokens. Timing depends on confirmation and monitoring; previews do not test every live-data condition. [Customize alerts](/spawnmeme-docs/feature-guides/telegram-and-promotion/29-buybot-customization.md) or [use Trending](/spawnmeme-docs/feature-guides/telegram-and-promotion/30-trending.md).

## Token refresh and private alerts

The shared five-minute refresh records supported tokens’ SOL raised and market cap, marks graduation when the curve completes, and sends [private token alerts](/spawnmeme-docs/feature-guides/telegram-and-promotion/43-token-alerts.md). Price alerts stop at graduation; Curve milestones can notify the graduation event. This does not extend Buy Bot trade monitoring to graduated pools. Refresh delays can delay notifications.

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/telegram-and-promotion/28-buybot-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.