Event Triggers
Trigger a Cloud Function when data in a table type is created (via insert or upsert), updated (via update or upsert), or deleted.
AdminKJ Jeyaram
(Admin, Google, LLC - Firebase)
shared this idea
-
Jimmy Chan commented
This is key for firebase event driven architectures.
-
Lincoln Rychecky commented
Without this feature, we can't simply keep our data synced with our Typesense instance.
Event triggers are probably one of the single biggest features our team needs.
-
Tim Richardson commented
I echo the thoughts of others in here, this feels like an essential feature. Certainly for us, I don't think we could migrate without it which would be a shame.
-
Nils Karlsson commented
Very important for all of our apps, we heavily rely on triggers for many backend processing tasks as well as push notifications. Would love to migrate over to data connect if this get's implemented!
-
Marcel Hoppe commented
Very much looking forward to this feature! onCreate or even more fine grained onUpdate triggers would be amazing.
-
Hassan Raza commented
i also trigger by event https://angelcityinsider.com/
-
Tim Lloyd commented
Super important for complex systems. Triggers and functions are key benefits to using Firestore and for those that would prefer a relational database using FDC they would be essential for recreating features. For example, I'd like a trigger on table writes so that I can audit who made the change, and when, etc
-
Tsortanidis Christos commented
Maybe triggers could be defined by mutation instead of table type events
-
Alex Patterson commented
Totally thought this was built in already, for sure need this!
-
David Oort Alonso commented
This would be huge for us given how used we are to this workflow on Firestore!
-
Roland Szpond commented
Could even watch for column changes to a particular row onChange({table_name}/{row_id}/{column_name}) or whatever they come up with.
-
Gabriel Mbugua commented
This feels like a must have feature.