How to use Configuration: lead channels

What this section is for

Connects Telegram/email channels, secrets and test lead delivery.

Before you start

You need access to IAM.Bot, the correct tenant/workspace and permission to change this configuration. Prepare a non-sensitive example value such as lead-test@example.com.

Buttons and forms

Control	What it does
Telegram	Performs the action named in the interface. Review the resulting state or message before continuing.
Email	Performs the action named in the interface. Review the resulting state or message before continuing.
Reveal secret	Performs the action named in the interface. Review the resulting state or message before continuing.
Copy	Copies the displayed value; verify that it does not contain a secret before sharing it.
Test channel	Runs a check or dry run so the result can be reviewed before production use.
Save	Validates the visible form and persists the current values.

Primary path in the interface

Open the application link above and sign in with the least-privileged role required for this section.
Select the intended tenant or workspace. Do not continue while the header shows a different tenant.
In the navigation, click Configuration: lead channels. The expected address is https://app.iambot.ru/config.
Click Save. Enter the documented safe values: lead-test@example.com. Do not paste a production secret into a free-text field.
Review every field before the final Save, Run, Publish or Confirm action. If a preview or validation control exists, run it first.
Review the validation message or changed row. The result must match this purpose: Connects Telegram/email channels, secrets and test lead delivery.
Only then continue to the next dependent section. Copy the request/correlation ID when the interface shows one.

Second path: direct link and CLI/API

Open the deep link https://app.iambot.ru/config instead of navigating through the sidebar.
Confirm the tenant/workspace after the page loads; a deep link must not silently switch scope.
Before automating the API path, run this product-specific read-only or validation command. It proves reachability but does not bypass application permissions:

curl --fail --silent --show-error https://cdn.iambot.ru/widget.js -o /tmp/iambot-widget.js
wc -c /tmp/iambot-widget.js

How to verify the result

A test lead is delivered once to both enabled channels and the secret is masked after saving.

If it did not work

Symptom	What to do
401 / sign-in screen	Sign in again, then return to this page. Do not put a session token in a URL.
403	Check the selected tenant and request the documented role; retrying with the same role will not help.
404	Verify the exact path and whether the feature is enabled in this environment.
409	Search for an object named `lead-test@example.com`; continue with it or choose a unique name.
422 / validation error	Correct only the highlighted fields. Keep identifiers lowercase unless the form explicitly allows otherwise.
429	Wait for the displayed retry interval or reduce the request scope; do not start parallel retries.
5xx / timeout	Refresh once after the server has recovered; do not repeat a destructive action while its result is unknown. Save the correlation ID and timestamp for support.