Like many partners, we are stoked that Forge Automation Actions is now generally available , thanks for delivering on this long awaited extension point 
The Automation platform has recently introduced/expanded the concept of a connection for a rule, seemingly capturing both the owner and the external authentication (if required), which makes a lot of sense as such:
A connection in Automation is a link that is created between your rule and a third-party product or application with which Atlassian has a supported integration.
However, while this ‘Connect’ flow is now also surfaced for Forge actions, there does not seem to be an SPI to use it?
This results in slightly weird UX where customers click on the ‘Connect’ button …:
… and then progress right to the action configuration without any discernible effect (I realize that the action owner is set under the hood, see PS):
In contrast, Atlassian’s actions use an interim modal to configure the connection, see e.g. for the built-in “Run SSM document” action:
It seems odd that the action transitioned to GA without this capability, so maybe I’m just missing how to use this configuration modal SPI due to incomplete docs (similar to the missing docs for the Smart Values SPI), and if not, when can we this expect partner action support for this core automation UX/SPI?
PS: These ‘empty’ connections for custom actions are nicely managed alongside the built-in ones already btw. (and can also be reused within a rule accordingly), so the only missing part seems to be the configuration modal SPI indeed:
