Overview
Custom Actions let you add your own handling for taps in a No-Code screen. Unlike built-in actions (purchase, restore, close, etc.), a Custom Action is not executed by the SDK — it is handed over to your app through the No-Codes delegate, and your code decides what happens. Each Custom Action is configured with a value — an arbitrary string that identifies the action, so your app code can tell which one was triggered. Use Custom Actions to run app-specific logic right from a No-Code screen, for example:- Open a native screen of your app
- Start a support chat
- Log a custom analytics event
- Toggle an app feature
Configuration
To configure a Custom Action in the No-Code Builder:- Select a component
- In the Action section of the right sidebar, choose Custom action
- Enter the Value — the string your app code will use to identify this action
Custom Actions are available for mobile screens only. For Web Funnel screens the action is not offered in the builder — there is no SDK delegate on the web to receive it.
Handling in Your App
When a Custom Action is triggered, the SDK fires the standard action lifecycle callbacks (started → finished) and, in between, calls a dedicated delegate method. The configured value tells your code which action to run:- The SDK performs no built-in handling — the whole behavior is up to your app code.
- The screen stays open. Close it with
NoCodes.shared.close()(iOS) /NoCodes.shared.close()(Android) if your custom logic requires it. - If no value was configured for the action, an empty string is delivered.
Cross-platform SDKs (React Native, Flutter, Unity, Cordova, Capacitor) support for Custom Actions is coming soon.
Minimum SDK Versions
Custom Actions require the following minimum SDK versions:Note
Older SDK versions silently ignore Custom Actions — tapping the element does nothing, and no delegate callbacks are fired.Success and Failure Actions Using No-Codes with custom purchases handling