No code required

Wire a click to real Salesforce actions

Navigate, update records, launch Flows, fire a toast. Configure it in the component, no Apex, no event handler.

Start freeExplore Dynamic Components
50+
interactions ready to wire
0
lines of Apex, no event handlers
Any
action: navigate, update, launch, toast
How it works

A click becomes an action in three steps

No triggers to register, no handlers to write. You configure the behavior right in the component, and it runs on the platform your data already lives on.

1

Pick what the user does

A button click, a row selection, a value change. The component already knows the events it can fire.

2

Choose an interaction

Navigate, Update Record, Execute Flow, Show Toast, Open Confirm. Chain several to run in order.

3

It just runs

Salesforce handles the navigation, the DML, the modal. You wrote no Apex and no event listener.

Navigate
Update Record
Execute Flow
Show Toast
Open Confirm
Open Quick Action
Refresh Query
Download
In every package

The same idea, wherever you build

Wire clicks to actions in the builder you already use. Each package brings its own set, tuned to where it runs.

Flow Screen Components

Guided processes

Move between screens, celebrate a finish, refresh data after a save.

Flow NavigationFire ConfettiRefresh All Queries
Learn more
Dynamic Components

Lightning pages

Open a component in a panel, call an agent, run a Flow in the background.

Open Dynamic Component PanelInvoke AgentforceExecute Flow
Learn more
Experience Cloud Components

Portals and sites

Guide visitors, confirm an action, launch a Flow without leaving the page.

NavigateOpen ConfirmOpen Flow Dialog
Learn more
LWC Components

Your own code

In code, components emit events you handle yourself. The no-code interaction engine lives in the builders above.

Component events
Learn more
Use cases

What teams wire up first

Act on a record from a table

Select rows, hit a button, update or delete them, then refresh the view. No screen change, no Apex.

Launch a Flow in context

Open a guided Flow in a dialog or side panel, pass the current record in, and refresh when it finishes.

Confirm, then commit

Ask for confirmation before a destructive action, show a toast on success, and route the user onward.

Why it matters

The behavior lives in the component, not in your codebase

On the platform, wiring a click to a real action usually means an Apex controller or an LWC event handler, code you write, test, and deploy. Avonni keeps that same behavior in the component configuration, so an admin can set it up and change it later without a release.

The platform way
The Avonni way
On the platform

Custom click behavior is wired in code and shipped through a deployment.

With Avonni

The same behavior is configured in the component and edited in place, no deploy.

FAQ

Questions about interactions

Which packages have interactions?

The no-code interaction engine is in Flow Screen Components, Dynamic Components, and Experience Cloud Components. LWC Components emit events you handle in your own code.

Do I need to write Apex?

No. Interactions call navigation, record operations, Flows, and modals through configuration. You add no Apex and no event listeners.

Can one click run several actions?

Yes. You chain interactions so they run in order, for example open a confirmation, update the records, then show a toast.

Can I launch a Flow from a component?

Yes. Run a Flow in a dialog or a side panel, or execute one in the background, and pass the current record in as a variable.

Is it free to try?

Yes. Every Avonni plan starts free with 10 licenses and no time limit, installed from the AppExchange into your own org.

Give your components something to do

Wire your first click to a real Salesforce action today. Start free with 10 licenses, straight from the AppExchange.

Start freeTalk to sales