For Internal Tools

The internal tools your team stopped asking IT for

Guided intake, mass edits, and team consoles your admins build in a Screen Flow instead of rebuilding the same forms by hand every quarter.

Explore Flow Screen ComponentsRequest a Demo
70+
Flow Screen components
No code
configured in Flow
85+
across the suite
What you build

The tools your team actually needs

Guided intake flow

Walk people through a request field by field so the data lands clean the first time.

Mass edit console

Update dozens of records inline in one table instead of opening them one by one.

Approval cockpit

Give a team one screen to review, act on, and track what is waiting on them.

Where to build it

Two ways to ship a tool

For internal tools
Guided, step by step

Flow Screen Components

70+ components for capture and review inside a Screen Flow: inputs, tables, pickers, and confirmations, wired to your objects.

Learn more →
Always-on consoles

Dynamic Components

Build the standing dashboards and record pages your team returns to every day, no Flow required.

Learn more →
The building blocks

Capture it, then show it back

25+Inputs

Everything for capturing clean data in a Flow.

Input TextText AreaComboboxDual ListboxCounterDate RangeTime RangeInput PenColor PickerIcon PickerSlider+14 more
20+Displays

Everything for showing that data back to the team.

Data TableKanbanListTimelineMetricChartFormatted ValueProgress IndicatorTreeMap+10 more
Mass editing

Edit the whole list, not one record at a time

1 screen
Avonni mass edit
Filter, edit inline, and save the whole set from a single table.
vs
1 by 1
Record by record
Open, edit, save, go back, repeat for every record on the list.

Same data, same permissions. The difference is how many clicks it takes your team to get through it.

From a Salesforce team
The flexibility is unparalleled. We considered building our own components, but Avonni was the clear top choice.
Tyler Teachman
Hitachi High-Tech America
In a real org

A site survey, built on one Map.

Avonni Map in step 2 of a Salesforce screen flow: a roof outline drawn as a polygon on OpenStreetMap tiles, with drawing tools and a Save survey button
center
Screen Flows

Site survey inside a flow

A technician traces the roof on a live map, in step 2 of a screen flow, and the shape is saved as a file on the work order.

See the configuration
All use cases
FAQ

Questions about internal tools

Do I need a developer to build these tools?

No. Admins build guided Flows and consoles with clicks. The components handle the parts that would otherwise need custom code.

Does mass editing respect our permissions?

Yes. Edits run through your Salesforce sharing rules and field-level security, the same as any standard record update.

Can I use these components in a Screen Flow and on a page?

The Flow Screen components live in Screen Flows. For standing pages and consoles, the same suite includes Dynamic Components.

What kinds of input can I capture?

Text, numbers, dates, choices, signatures, and more, with validation built in so bad data does not make it through.

How is it licensed?

Every plan includes all three packages. You can start free with 10 licenses and scale as your team grows.

Build the tool instead of the ticket

Give your team guided intake, mass editing, and consoles they configure themselves, on the platform your data already lives on.

Explore Flow Screen ComponentsRequest a Demo