# Connecting the bot on the constructor
For bots built with constructors, we recommend using the [auto connection method.](/en/connect-bot.md)
## What should you check when connecting?
Before using UTM tags, we recommend checking whether your bot supports additional parameters in start. (Some constructors do not allow working with this parameter.) To do this, create a link like this for your bot:
```url
https://t.me/graspil_bot?start=test
```
Replace graspil\_bot with your bot’s username, open this link in your browser, follow it, and launch the bot. If your bot reacts as usual (for example, sends the default start message), it means you can use UTM tags.
{% hint style="warning" %}
If you have already launched the bot before, this launch may be considered a repeated start. Some bots are configured not to react to repeated launches or react differently than you might expect. Send the /start command in the bot to see how it responds to repeated starts without parameters.
{% endhint %}
## Platforms that can be connected via API
puzzlebot.top
In Graspil, when connecting a bot, select the API method (if you didn’t initially choose this method, you can proceed with the following steps in the instructions, and the method will automatically change once the system starts receiving data).
Go to your platform’s dashboard and select the desired bot. Navigate to ***Settings*** -> ***Integrations*** -> ***Outgoing Requests***
Set the URL: `https://api.graspil.com/api/send-update`
Check the option “**Set header list**” and add the following header:
Key: `Api-Key`
Value: insert your Graspil API key
### Where to find the API key?
You can find the key in your Graspil dashboard, under [*My Bots*](https://app.graspil.com/bots). Select the relevant bot and click on the key icon; a window with the key will appear.
**Attention!**
After making all the changes, **interact with the bot** (e.g., send the /start command) so that Graspil receives the first data. Within a few minutes, the status of your bot will change to “connected.”
salebot.pro
In Graspil, when connecting a bot, select the API method (if you didn’t initially choose this method, you can proceed with the following steps in the instructions, and the method will automatically change once the system starts receiving data).
In **Sale**Bot, select the desired project and go to the project **settings**. Find the ***Constants*** section and add the constant: `save_webhook=1.`
Go to the ***General Settings*** section and fill in the ***Webhook URL*** field:
Webhook URL: `https://api.graspil.com/v1/send-update-salebot?api-key=`**`replace_with_your_graspil_API_key`**
### Where to find the API key?
You can find the key in your Graspil dashboard, under [*My Bots*](https://app.graspil.com/bots). Select the relevant bot and click on the key icon; a window with the key will appear.
**Attention!**
After making all the changes, **interact with the bot** (e.g., send the /start command) so that Graspil receives the first data. Within a few minutes, the status of your bot will change to “connected.”
## Transmitting additional events/conversions
\
If you want to send additional events to Graspil, such as “sale”, pay attention to the API [section on sending target events](/en/api/send-event.md). Often, platforms allow the setup of webhook sending upon specific events (e.g., a sale).
---
# 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.graspil.com/en/connect-bot/connecting-the-bot-on-the-constructor.md?ask=
```
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.