✅ Add Kanban view for Custom Objects
I
Iver Aune
If you are not familiar with the term Kanban, it is the setup we have for Opportunities.
View picture.
Add custom statuses like we have in Opportunities for Stages to the Kanban view.
Photo Viewer
View photos in a modal
Log In
A
Aayush Singhal
Merged in a post:
Opportunities In Custom Object Workflows
M
Marina Abramson
Need the ability to see & control pipeline stages in custom object workflows.
Use case:
I have an event planning company and I create Custom Object "Event".
Event has different stages to its' lifecycle and i need to move it along the way of the pipeline (not the contact).
Same thing with Custom Object Shift.
Each event has shifts associated to it that the staff is assigned to.
The shifts have different states: Job Offered, Accepted, No-Show, Completed.
A
Adrian King
Yes please!!!
Much needed.
A
Ashley Haas
I need this to for my clients who have estimates and we need to track the stage they are in. Thank you!
S
Sales & Marketing
Merged in a post:
🚀 Feature: Kanban for Custom Objects (Stage-Based Pipelines)
F
Frank Felix
Problem
Custom Objects currently only support list view. This makes them difficult to use for managing real operational workflows.
Teams that use Custom Objects for things like service orders, projects, or internal processes lack a visual way to track progress. This creates friction, reduces adoption, and forces teams to rely on external tools.
Proposed Solution
Allow Custom Objects to have a Kanban (pipeline-style) view with stages, similar to Opportunities.
Users should be able to:
Define stages for any Custom Object
View records in a Kanban board
Move records across stages using drag & drop
Automatically update status when moved
Example Use Case
A “Service Orders” Custom Object could have stages like:
Received
Diagnosis
In Progress
Waiting for Parts
Ready
Completed
This allows teams to manage operations visually instead of using static lists.
Key Clarification
This should not replace the sales pipeline.
Opportunities → Sales process
Custom Object Kanban → Operational workflows
Both should coexist independently.
Impact
Improves usability and adoption
Provides real-time operational visibility
Reduces dependency on external tools (like spreadsheets)
Enables better workflow management inside GHL
Conclusion
Custom Objects today act mostly as data storage.
With a Kanban view, they become a true operational management tool, making GHL significantly more powerful for real-world use cases.
F
Frank Felix
We need to enable a Kanban (pipeline-style) view for Custom Objects.
Right now, Custom Objects are limited to list view, which makes them hard to use for operational workflows. This creates friction for teams that need to manage processes visually, like service orders, projects, or internal operations.
The idea is simple: allow Custom Objects to have stages, just like opportunities, and let users move records across those stages in a Kanban board.
For example, in a service operation, a Custom Object like “Service Orders” could have stages such as:
Received, Diagnosis, In Progress, Waiting for Parts, Ready, Completed.
Users should be able to drag and drop records between stages, and each movement should update the record’s status and optionally trigger automations.
This would not replace the sales pipeline. It would be a separate operational layer. Opportunities remain for sales, while Custom Object pipelines would handle execution and operations.
This feature would significantly improve usability, adoption, and real-time visibility for teams managing workflows inside Custom Objects.
Right now, Custom Objects feel like static storage. With this, they become a real operational tool.
Chase Buckner
Merged in a post:
Ability to Add Objects to Pipelines, Not Just Contacts
B
Brad Matthews
It would be great if a custom object - In our case 'Properties', were able to be added to a pipeline so we can make use of the Kanban view.
We'd like to set up a 'Deals' pipeline and track the status of a property. Right now, we have 'Properties' set up as a custom object, but need a Kanban view.
It seems like contacts are the only object that's able to be added to pipelines.
Ideally, make objects act just like contacts. Ability to add to opportunities, Kanban views, all automation functionality, etc.
V
Victor Oben
A
Aayush Singhal
Merged in a post:
A card view like Opportunities could be cool, a custom view not just List view would be great, to make our own UI for the CO.
D
Daniel Cowart
A
Aayush Singhal
Merged in a post:
Pipeline for custom objects
A
Aryeh Hirsch
We need custom objects to have the same functionality as the original Opportunities, for different steps of an operation.
J
John Naccarato.
100% needed. We are used to it with Opportunities so it makes perfect sense.
Load More
→