Custom Objects Now Available in Client App Builder

TL;DR

Client App Builder now creates and connects Custom Objects directly to sub-account CRMs using AI prompts. Test the feature in Labs if you manage client portals or branded mobile apps.

Who this affects

HighLevel has not confirmed which subscription plans or account tiers have access to this update. Agencies managing web-based Client Portals, branded mobile apps, or Vibe Coding setups inside sub-accounts will use this directly. Agencies not using the portal builder can skip it.

What changed

• AI-powered creation: Custom Objects can now be generated inside Client App Builder from natural language descriptions.
• Direct CRM sync: Member submissions through the portal save directly as Custom Object records in the sub-account CRM.
• Pre-creation review: Preview screens display proposed data structures, sample records, and access permissions before objects are finalized.
• Automatic page generation: The system builds dedicated portal pages for members to view and submit their records.
• Granular visibility controls: Access can be configured for individual member records, company-level records, or read-only access across all records.
• Integrated payments: Payment actions can be triggered on records using HighLevel invoices when a payment provider is connected.
• Technical limits: Object creation allows up to 3 objects per prompt, bound by the standard CRM ceiling of 10 custom objects per sub-account.
• Platform availability: The feature supports web-based Client Portals, Vibe Coding experiences, and branded mobile apps.
• Rollout and gating: HighLevel has not confirmed rollout milestones or plan-level gating.

Where to find it

Go to Labs > Client App Builder within your HighLevel account.

How agencies will use this

An agency setting up an intake portal in a sub-account can describe the required data structure using natural language inside Client App Builder. After reviewing the generated fields, access permissions, and sample records on the preview screen, the agency confirms creation, up to 3 objects at a time within the 10-object sub-account limit. The builder automatically deploys the portal pages for end users to input data. From there, the agency sets visibility permissions so users only view individual or company records, and connects a payment provider to trigger HighLevel invoices directly against those records.

Our take

This is a major architectural step for the portal builder. It removes the need for manual workarounds to route portal form data into CRM custom objects. Be mindful of the 10 custom object cap per sub-account before mapping out complex structures, and remember that it is currently labeled under Labs.