For automation power-users who want Port to be the control plane and source of truth from which the ancillary data sources are updated, the ability to use the audit log as a basis for automation triggers would be ideal. The reason for this is that some automation backend logic can ideally be shared between many property changes, entity updates, etc.

Essentially, automations today are very fine-tuned on specific changes that occur. For example: if service health is degraded below a certain threshold, then trigger the automation that rolls the service back.

Ideal example: multi-condition, multi-trigger, shared logic for a single automation (if service health degrades below threshold OR if incident occurs for service OR if service is locked -> then run x automation).