Take your Screen Flows to the next level. 70+ drag-and-drop components that extend the standard Flow screen library. Configure visually, ship without code.
Each clip is an Avonni component on a flow screen, working on real Salesforce records. What the user does comes back to the flow.
Same org, same records, same gesture. Switch between the standard component and Avonni.
25+ column types with inline editing, filtering, sorting and row actions. Users select and edit records in place, and the flow gets the results back.
See the Data Table on every surface →
Plot any set of records with custom markers and live geolocation. Users pick a place on the map and the flow gets the answer.
See the Map on every surface →
Day, week and month views bound to your records. Users browse availability and pick a slot without leaving the screen.
See the Calendar on every surface →
Search any object with filters and a preview of each result. Cleaner than a lookup, faster than scrolling a table.

Visual pickers, color pickers, icon pickers, sliders and ratings. Capture structured answers with a tap instead of a free-text field.

Users drop a CSV onto the screen and the parser turns it into records the flow can loop over. Bulk work becomes a screen, not an admin ticket.

Components that turn the phone into an input, right on the flow screen.
Every component opens in the built-in Component Builder: map your Salesforce data, tweak every property, and preview the result live before it ever reaches a user.

A Deal Review flow on the account page: a Data Table of open deals, cards for the next step, and one Update Records. No code.
Tell Claude, Cursor or Copilot what the screen should do. With the Avonni skill and MCP server, it picks real Flow Screen Components, writes the flow file with documented properties only, and validates it before you deploy.
Shown in Claude Code
The avonni-flow-components skill plans the screen, checks each component against the Avonni MCP server and validates the flow file. You review, then deploy.
Works with Claude, Cursor, Copilot, Gemini and Agentforce
The same components underneath. What changes is where you build, and who does the building.
One component, dropped straight onto a Lightning page.
Several components assembled into one custom layout.
Portals and community sites, in your brand.
Wizards and intake forms inside Flow Builder.
The same components, as tags in your own code.
Most teams pair Flow Screen Components with Dynamic Components: pages for what users see, Flows for what they do.
Each one comes with its configuration. Three were filmed in a real org, three were built by an AI assistant from a single sentence.
No. Every component is configured visually in the built-in Component Builder, with a live preview. If you can build a screen flow, you can use Avonni.
Yes. Avonni Flow Screen Components is distributed on the AppExchange and has passed the Salesforce security review. It installs as a managed package in minutes.
You get 10 free production licenses and unlimited sandbox use. Paid plans scale by users when you are ready to roll out to a larger team.
Yes. Avonni components are standard flow screen components: drop them into any existing screen flow next to the elements you already use.
Avonni extends the base Lightning library with 70+ components: data tables with inline editing, Kanban boards, maps, calendars, signature capture and more, each with built-in interactions.
Install from the AppExchange and build your first screen in minutes. 10 production licenses on us.
Available on the AppExchange