t.me/your_bot?start=<prefix><code>. The builder saves the start parameter for the subscriber.https://clck.now/hook/wh_… — the key is already in the address.{"click_id": "<subscriber's start parameter>", "event": "paid", "value": 990, "order_id": "<order number>", "user_id": "<subscriber id>"}data.variables.start) and event renaming (Payment=paid) in the webhook settings.The default amount is in rubles. A repeat with the same order_id does not create a second event. Response: 201 created, 200 repeat, 404 click not found, 400 data error; the last request and error are visible in the dashboard.
"HTTP request" (or "Webhook") block: POST method, JSON type. The click code comes from the parameter the person arrived with via the t.me/bot?start=… link (in Salebot it is available in the client variable, usually start/start_param — check the client card).
"Send webhook" action: POST, JSON. BotHelp stores the subscriber's start parameter in a field (ref/tag from the link) — put it in click_id.
"Webhook" / "HTTP request" block: POST, JSON. The value from the ?start=… link is in the contact variable (start tag) — put it in click_id.
"HTTP request" (API request) command: POST, JSON. Save the /start parameter to a variable and pass it in click_id.
"Webhook" trigger/action: POST, JSON. The start parameter is in the contact variable (UTM/ref from the link) — put it in click_id.
Any system that can send an HTTP request: POST JSON, form or GET with parameters. Field paths are set below.
Block and variable names in builders change from version to version — check their documentation; the universal webhook will parse any JSON by paths.