If this was my Environment, I would probably go into the database and add the hash column manually. If that isn’t enough I would simply put in the hash values myself.
ps. it is not a problem of the trigger node it self, it is the workflow that is missing the hash column in the database. That is why all types of trigger nodes are affected.
I guess n8n checks something with the hash before setting it active.
Now it seems like I can suddenly save it without the error. I just removed it and added it again and also had to insert the developer API key in the Hubspot trigger node which I didn’t have prior to that.