Triggers

A trigger is where the chain starts. The event happened — the chain runs. There are five kinds, and they are not interchangeable.

Command

/start, /menu, /support — what a person types to the bot or picks from the menu. A command can be shown in the Telegram menu with a description and an order, or kept hidden: a hidden one still works when typed by hand.

make a /menu command labelled "Menu and order" that opens the storefront

Keyword

The chain starts when a word or phrase appears in a message: "price", "delivery", "hello". Matching is exact or "contains".

when someone writes "delivery" — send the delivery terms and an order button

Button on the site

The person pressed "Submit" in a form or "Book" on a page of the site — the site passes the data, and the chain receives it already validated: name required, e-mail only as an e-mail. Then: write to data, confirm to the person, notify the owner.

when the booking form is submitted on the site — save it and message me

System event

Joined a channel, left, arrived through a link, opened the site — the platform records events. Choose a supported event in the editor to start a chain.

when someone joins the channel — tag them "subscriber" and say hello

Owner button

An action only you run: from the user card in the workspace or through the agent. "Approve the request", "Refund", "Unban". The user doesn't see such a button and can't invoke it.

make a "Confirm booking" button: changes the status and messages the person

Payment is not a trigger

The "Pay" button opens an invoice but doesn't start a chain. Everything that happens to the order next is caught by the offer lifecycle node — it has its own events: order created, paid, failed, cancelled, refunded. See "Waits and payment".