Skip to main content
App builderWeb

Add feedback and local interactions

Show useful feedback and configure supported browser and client interactions.

1 min readBuild at your own paceOpen Apps

The workflow menu's Interaction group contains Toggle Dark Mode, Open alert, Show toast, Push notification, Show Element, Telegram Action, Play vibration, Save To Local Storage, Save To Component, and Share Content.

Configure the smallest useful response​

Select the trigger element, add the interaction, and complete its fields. A toast can acknowledge a finished operation; an alert or confirmation can ask the person to make a decision; Show Element changes the visibility of an intended target.

FOLLOW ALONGFrom a button to a workflow

Open the right flow, add an action, and configure its result.

Example project
Show toast action selected on the workflow canvas with Toast Title, Duration, Position, and Save in the right settings panel.
Full interface

A node needs real settings. Enter the message, choose duration and position, and save the action. Then test the complete sequence in Preview.

Web interface captured on 5 Nov 2026 with example content. Choose a numbered note to take a closer look.

Configure & saveAppStruct web interface · example project
Show toast action selected on the workflow canvas with Toast Title, Duration, Position, and Save in the right settings panel.

Keep platform behavior explicit​

Some interactions need a particular environment. Telegram Action expects a Telegram Mini App context for its Telegram-specific controls. Push notification settings require the mobile publishing and Firebase setup displayed by the editor; do not treat that action as a configured web-push service.

Browser support also affects vibration and sharing. Provide a visible button or message that still makes the main task understandable when a device feature is unavailable.

Use local storage appropriately​

Save To Local Storage keeps a value in that browser's local storage. It is different from writing a shared backend record and should not be described as account-wide synchronization.

Test a completed operation and an unsuccessful operation. Keep success feedback tied to the actual result rather than showing it solely because a button was clicked.

Have a question?Find an answer in the FAQ