Tapo's automations are limited to the Tapo ecosystem of devices in their actions.

An easy way to fix this is the ability to add an action to an automation that can pass the trigger events as JSON to an HTTP enpoint.

It would just require a text input for the the URI to call, and the ability to set a list of key/value headers that would be added to the request (ie bearer token) . You could also have a dropdown list of HTTP request methods, GET, PUT, POST - but you could simply make it a POST.