Skip to main content
New Idea

Allow Real-Time Rule Events Based on Custom Objects

Related products:CS Rules Engine
  • April 28, 2023
  • 10 replies
  • 254 views

jenlpro
Forum|alt.badge.img+4

I have a use case where we have a custom, low-volume object called Value Case which we use to track customer-reported ROI. We have a stage-like dropdown field on this object, and we need to keep track of each record’s stage movement. For example, if a record is saved on creation in Stage 1, and later the record is modified to Stage 2, we need to be able to see which date the record moved from Stage 1 to Stage 2. 

However, we anticipate there being several fringe cases or human errors that cause Stage 1 to move to Stage 2 and back to Stage 1, OR for Stage 1 to move to Stage 3 accidentally, when it should move to Stage 2. We want to use Real-Time Rules to capture the movement in (close to) realtime to store this movement in a custom object called Value Case Revision Dates. 

Given the current limitations on realtime rules, we are only able to configure these rules using limited Internal Events as the trigger: Company, Call to Action, CS Task, Relationship, and Relationship Type. 

For Real-Time rules to truly be impactful for our organization, we would need the ability to run them based on custom object events. 

10 replies

  • Contributor ⭐️⭐️⭐️
  • October 4, 2023

This would be really helpful to us as well. We would really like to be able to track several fields on a custom object so we can see when they were last modified, but that doesn’t seem to be an option without this.


TMaier
Forum|alt.badge.img+5
  • Helper ⭐️
  • October 4, 2023

From what I’ve heard, change tracking is like THE primary use for realtime rules right now - and it works really well for the supported subjects. Expanding the supported subjects seems like a clear win for everyone.


romihache
Forum|alt.badge.img+9
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • October 5, 2023

Great idea! I can think of several ways to leverage this functionality!
 


  • Contributor ⭐️⭐️⭐️
  • March 14, 2024

Has there been any consideration of this idea (or even some other way to track field history)? I find myself wanting to be able to track field history on custom objects on a regular basis, but being unable to.


alizee
Forum|alt.badge.img+13
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • September 3, 2025

Absolutely required. I need to track changes on a relationship person object and… not supported :(.


dayn.johnson
Forum|alt.badge.img+8
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • September 5, 2025

@kim_stone, ​@kstim – would this functionality be required for our CSM/PM tracking? At first glance, sounds like it. We need to be able to track changes on custom objects.


kim_stone
Forum|alt.badge.img+1
  • Contributor ⭐️⭐️
  • September 5, 2025

@kim_stone, ​@kstim – would this functionality be required for our CSM/PM tracking? At first glance, sounds like it. We need to be able to track changes on custom objects.

This would definitely provide much more insights for the internal field teams while working through the customer journey! Right now there is no way to know who changed what and for what reason, which causes a lot of side conversations/questions via Slack or email...


kstim
Forum|alt.badge.img+7
  • Helper ⭐️⭐️
  • September 5, 2025

@dayn.johnson We don’t currently use real time rules much due to their limitations, but this would be nice to have!


dayn.johnson
Forum|alt.badge.img+8
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • September 5, 2025

We don’t currently use real time rules much due to their limitations...

This statement should raise some red flags.

❗Also

 

This would definitely provide much more insights for the internal field teams while working through the customer journey! Right now there is no way to know who changed what and for what reason, which causes a lot of side conversations/questions via Slack or email...

@kim_stone, you’ll 100% be interested in this post:

 


Sashank Goparaju
Forum|alt.badge.img+6

We have a strong use case where key Gainsight data stored in custom objects needs to be pushed to external systems in near real time whenever specific fields change. Today, the lack of Real-Time Rule support for custom object events forces us to rely on scheduled rules or indirect workarounds, which adds latency and operational complexity. Enabling Real-Time Rules on custom objects would allow us to reliably synchronize critical updates with downstream systems and significantly improve process efficiency and data accuracy.

We also strongly support the field history tracking use case on custom objects, specifically the ability to capture who made a change and exactly which fields were modified.