We have created an OAuth M2M user which we are planning to use to programmatically trigger shared automation runs (i.e. run automations that are in a shared space). The idea would be for the M2M user to be able to trigger any automation inside the space, regardless of who the owner of the automation is.
According to this post by @Emile_Koslowski, "members of a shared space will be able to run the automations over the /runs endpoint if they have sufficient permissions", so we added the "bot" user to the space and gave it full permissions on the space. However, when using the/runs endpoint, we still get a HTTP 403 - No Permission error, and the documentation for the /runs endpoint does mention that "the requesting user must be the owner of the automation."
Is this because we are still missing some permission or what we are trying to do is currently not possible? Has anyone managed to use the automations /runs endpoint to trigger an automation owned by another user?
We can still set the automations to "triggered" and run them with the webhook (automations/<id>/actions/execute), but that would require handling a separate X-Execution-Token for every automation, while we would rather have a single OAuth service user which is able to run any shared automation from a specific space.
