No code required

Connect any Salesforce object, without writing a query

Point a component at an object, pick fields by name, add conditions, and pull related records. No SOQL, no Apex, no wrapper class.

Start freeExplore Dynamic Components
Any
standard or custom object, by API name
0
SOQL or Apex to read your data
Related
records follow your object relationships
How it works

Configure the data, skip the query

A data source is a few choices in the builder, not a class to write and deploy. The component reads live from your org.

1

Choose an object

Pick any standard or custom object by its API name. The component knows the fields it can read.

2

Pick fields and conditions

Select fields, add filter conditions, set a sort order and a limit. Give users search and cascading filters too.

3

Bring in related records

Follow relationships to pull child and related records, and show them in tables, trees, or relationship graphs.

Any object
Fields by API name
Filter conditions
Sort and limit
Search fields
Related records
Pagination
In every package

Query where you build

The same no-code data source powers the builders that read Salesforce records, tuned to where each one runs.

Dynamic Components

Lightning pages

Query any object, add conditions, and follow relationships to show related records in tables, trees, and graphs.

Query Data SourceRelated recordsFilters and search
Learn more
Flow Screen Components

Guided processes

Feed screens from a query or a Flow variable, so tables and lists show live records inside your Flow.

Query Data SourceVariable Data Source
Learn more
Experience Cloud Components

Portals and sites

Show your Salesforce data to portal users with the same query, filtering, and search, scoped to what they can see.

Query Data SourceFilters and search
Learn more
Use cases

What teams query first

A table on any object

Point a data table at accounts, cases, or a custom object, choose the columns, and let users filter and search.

Related records on a record page

Follow relationships from the record you are on to show its opportunities, contacts, or activities in context.

A live list on an app page

Build an app page around a query, with conditions and a sort order, and it stays in sync with your org.

Why it matters

The query lives in the component, not in a class you deploy

On the platform, reading related records into a custom screen often means a SOQL query inside an Apex controller and a wrapper class, written, tested, and deployed. Avonni keeps the query in the component configuration, so an admin can point it at an object and adjust the conditions without a release. For data outside Salesforce, pair it with Flow HTTP Callouts.

The platform way
The Avonni way
On the platform

The query lives in Apex and ships through a deployment.

With Avonni

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

FAQ

Questions about data sources

Do I need to write SOQL or Apex?

No. You choose an object, fields, conditions, and a sort order in the builder. The component reads the records for you, with no SOQL and no Apex.

Which objects can I query?

Any standard or custom object in your org, referenced by its API name. You choose which fields to read and show.

Can I show related records?

Yes. Follow relationships to pull child and related records, and display them in tables, trees, or relationship graphs.

Can I read data from outside Salesforce?

The data source reads records from your Salesforce org. For external systems, pair the components with Flow HTTP Callouts and feed the result in.

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.

Put your Salesforce data on screen

Connect your first object and show live records today, no query to write. Start free with 10 licenses from the AppExchange.

Start freeTalk to sales