🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!
Guides & Tutorials October 19, 2026

How to Display Gravity Forms Entries in Bricks Builder

GravityExtra
How to Display Gravity Forms Entries in Bricks Builder

Gravity Forms is one of the best ways to collect structured data on WordPress. Vendor applications, member profiles, event registrations, testimonials, job posts and support requests all end up as neat entries in your dashboard. Sooner or later, though, you want to show some of that data on the site itself: a directory of approved vendors, a wall of reviews, a list of upcoming talks, or a page where a customer can see what they sent you.

If your site is built with Bricks Builder, this is where it gets awkward. This tutorial explains why, compares the usual workarounds and then shows step by step how to display Gravity Forms entries in Bricks Builder with a real query loop, including filters, search, pagination and the privacy settings you should get right before anything goes live.

Why Gravity Forms entries do not show up in Bricks

The Bricks query loop is built around WordPress objects: posts, terms and users, plus a few special sources such as API results and arrays. Gravity Forms does not store entries as posts. It keeps them in its own database tables (entries and entry meta) and reads them through its own API, called GFAPI. Because of that, Bricks has no idea the entries exist. You will not find them in the query Type list, and the dynamic data picker has no tags for entry fields.

There are good reasons for this design. Separate tables keep large forms fast, and they keep form data out of the places where posts appear by default, such as search results and feeds. But it means that you need a bridge if you want to display entries.

The usual workarounds and their limits

1. Shortcodes and HTML tables

The quickest route is a shortcode that prints a table of entries, dropped into a Bricks Shortcode element. It works, but you lose everything that makes Bricks pleasant. The markup is fixed, so cards, grids and custom layouts mean CSS overrides. The builder canvas often shows nothing useful. And it is easy to publish more columns than you meant to, because the shortcode decides what to print.

2. Copying entries into a custom post type

Another popular approach is to create a post for every entry, either with a feed add-on or with a snippet hooked into form submission. Once the data is a post, the normal Bricks query loop works. The cost is maintenance: two copies of the same data, edits in one place that do not reach the other, deleted entries that leave orphaned posts, and file uploads that have to be copied into the media library. For a directory that changes every week this becomes a chore.

3. A custom query in PHP

Developers can write their own Bricks query type with the Bricks query filters and GFAPI. It is the cleanest result, but you have to handle pagination, caching, escaping, permissions and dynamic data tags yourself, and keep it working through Bricks and Gravity Forms updates. It is a lot of code for a list of vendors.

A better way: a Gravity Forms entries query type

The Gravity Forms Entries Query Loop for Bricks Builder adds a query type called Gravity Forms entries to the Bricks query loop. Entries are read live with GFAPI, so there is nothing to sync, and you design the repeated item with normal Bricks elements. Field values come in through dynamic data tags, the same way you would use {post_title} in a posts loop.

A Bricks page for the fictional Riverside Makers Market titled Meet this season's makers: six white cards in a three-column grid, each built from one Gravity Forms vendor application with a round logo, business name, owner name and city, an orange category pill, a short description, a bulleted product list, booth size and application date, and a dark Visit website button; below the grid the text 12 vendors and page links 1, 2 and next with the current page in orange
A public vendor directory: one Bricks card per Gravity Forms entry, with the Entries pagination element below.

Step 1: install the add-on and decide what may be public

  1. Install and activate the add-on, then enter your license key in Forms → Settings → Bricks Entries Loop.
  2. In the same tab, under Open loops, tick only the forms whose entries may be shown to visitors or to every logged-in user. Leave private forms unticked.

This second step matters. Every loop has a visibility rule, and the default is “users with a capability”, which means only people who could already view the entries in the Gravity Forms dashboard. Loops set to “Everyone” or “Any logged-in user” only work for forms on that allow-list. If you pick the wrong form in the builder by accident, the loop stays empty instead of leaking data.

Privacy checklist

  • Show only the fields you need. A tag prints exactly one field, so nothing appears unless you add it.
  • Ask for consent in the form when entries will be published, for example with a consent field.
  • Use a status such as “starred” or a field filter like “Approved is Yes” so only reviewed entries go public.
  • Never publish e-mail addresses or phone numbers in an open loop unless people agreed to it.

Step 2: create the query loop

  1. Open the page in Bricks and add a Container with a grid layout (for example three columns on desktop, one on mobile).
  2. Inside it add a Block. This Block becomes the card that repeats.
  3. Select the Block, turn on Query loop and set the query Type to Gravity Forms entries.
  4. Pick your form, set Who can see these entries and choose how many entries per page you want.

Step 3: design one entry with dynamic data

Add the elements of the card inside the Block. For a vendor directory that could be an Image, a Heading, a couple of Basic Text elements and a Button. Then fill them with tags:

  • {gf_entry:2} for the business name (field 2) in the Heading.
  • {gf_entry:1} for the full name, or {gf_entry:1.3} for the first name only.
  • {gf_entry:9.3} for the city part of an address field.
  • {gf_entry:7:url} in the Image element to show an uploaded logo.
  • {gf_entry:10} as the Button link for a website field.
  • {gf_entry_meta:date_created:j M Y} for the submission date in your own format.

List fields come out as a bulleted list, checkboxes as a comma separated list and prices in the currency of the entry. All values are escaped, so a visitor who types HTML or a script into your form cannot break your page.

Step 4: filter, search and sort

Most entry lists need some filtering. The query settings include the entry status (all active, starred, unread or read), payment status, entries of the current user and a repeater of field filters. Each filter takes a field ID, an operator and a value, and values can use dynamic data. Here are three patterns that cover most sites:

  • Approved only: add a radio field “Approved” to your form, set it in the entry editor and filter on Approved is Yes. Or simply star approved entries and choose “Starred entries”.
  • Category pages: filter the category field with {url_parameter:category} and link to /vendors/?category=Ceramics. One template, many lists.
  • Search box: put {url_parameter:q} in the Search setting and add a small GET form with an input named q above the loop. The loop shows entries that contain the text in any field.

Combine filters with “all” for narrow results, or switch to “any” to show entries that match at least one rule, for example ceramics or textiles. Sorting works by date submitted, date updated, entry ID or any field. For prices, booth sizes or scores tick Numeric sort so 12 comes after 9.

Step 5: add pagination

Set entries per page in the query settings, then add the Entries pagination element after the loop and select the loop. You get numbered links, previous and next arrows and an optional “Page 2 of 5” label, with style controls for colours, spacing and borders. Every loop keeps its page in its own URL parameter, so a page can hold several paged lists. If you prefer a “Load more” button or infinite scroll, use the Bricks options in the query settings: the add-on reports the number of pages to Bricks.

A Bricks table titled Vendor applications with a dark header row and five Gravity Forms entries: entry ID, business and contact name, email and multi-line studio address, category, a green payment status pill with the amount in pounds, the application date and the name of the user who submitted it; below the table 12 applications and page links 1, 2, 3 with the text Page 1 of 3
A private office table: the same entries as table rows, visible only to users who can view entries.

Example: a private dashboard table

Not every list is public. For an office team you can build a dashboard on a private page with the default visibility rule. Set a Block to the table tag, add a header row, and make the loop item a table row with cells for the entry ID, name, e-mail, payment status and date. Staff with the Gravity Forms “view entries” permission see the rows; everyone else sees your no-results text. Because the rule is checked for each request, a cached page or the Bricks query cache never shows the rows to the wrong person: the cache key includes the user and the page.

Example: “My submissions” for logged-in users

Set the visibility to Logged-in user, own entries only and the loop shows each user only the entries they submitted while logged in. This is ideal for application portals, member directories where members edit their own profile, or customers checking the status of a request. Add {gf_entry_meta:payment_status} to show whether a payment went through.

A Bricks page titled My applications for a logged-in vendor, showing only her own four Gravity Forms entries as cards with logo, business name, owner and city, category pill, description, product list, booth size, date and a Visit website button
“My applications”: the loop set to own entries shows a logged-in user only what they submitted.

Show Gravity Forms entries in Bricks without shortcodes

Get the Gravity Forms Entries Query Loop for Bricks Builder

Performance tips

  • Keep entries per page reasonable. Ten to thirty cards load fast; for longer lists use pagination or Load more.
  • Filter on fields with short values such as a category or a yes/no field. Searching across all fields of thousands of entries is slower than an exact match.
  • Each loop runs one query per page view and the result is cached for the rest of the request, so using the same loop twice on a page costs nothing extra.
  • Images from file upload fields are served at their original size. Ask applicants for reasonably sized logos, or set a fixed size on the Image element.

Frequently asked questions

Does it work with Gravity Forms 2.7 and newer?

Yes. The add-on uses GFAPI, available in every current Gravity Forms version, and it was tested with Gravity Forms 2.9 and 3.1.

Can visitors see entries of every form?

No. A loop open to visitors only works for forms you tick in the add-on settings, and new installs have nothing ticked. IP addresses and user agents are never available as tags.

Can I edit entries from the front end?

This add-on displays entries. To let users change their entries, combine it with a front-end editing solution and link to it from the loop with the entry ID tag.

Will it slow down my site?

No noticeable impact for normal lists. The add-on adds no JavaScript, only a tiny stylesheet for the pagination element, and it does not add jQuery.

Wrapping up

Displaying Gravity Forms entries in Bricks Builder no longer needs shortcodes, synced post types or custom PHP. Add the Gravity Forms entries query type to a loop, choose who may see the entries, design one item with Bricks elements and dynamic data tags, and let filters, search and pagination handle the rest. Start with a private dashboard to get familiar with the tags, then open up the forms that are meant to be public.

Show Gravity Forms entries in Bricks without shortcodes

Get the Gravity Forms Entries Query Loop for Bricks Builder

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr