Currently, if a field is deleted, and there is a workflow that was creating or updating an item using that field, the automation breaks until you update it to remove the deleted field.
This is tough to address when you have a lot of flows and don’t necessarily know which ones will be impacted by a deleted field.
Preferred Solution: Let me view a list of all flows (and even possibly calculations) that are using a field (see: QuivvyTools for Podio). That way, I can make the necessary updates before removing a field.
Bonus points if flows can ignore non-filled (i.e. deleted) fields, in case a user removes a field and forgets to check where it’s being used.
Backup Solution: Give us a workflow automation API, then we can build this ourselves 