Not only we need a way to trigger custom automations using the "Smart Buttons", but also the documentation has to be significantly improved - currently it vaguely suggests that it is possible, so it's misleading. It takes an effort to finally find this very issue to realize that "Smart Buttons" cannot trigger custom automations!

From the docs:

—

Managing smart buttons

Global and space admins can copy, edit, and delete the rules associated with a smart button in the Automation panel.

• https://support.atlassian.com/cloud-automation/docs/smart-buttons-for-automation-in-confluence/ 
• https://support.atlassian.com/cloud-automation/docs/edit-copy-and-delete-automation-rules-in-confluence-cloud/ 

I'm a little surprised that this needs to be a feature request, and not considered MVP - All of the automations that are pre-defined button actions are esoteric, limited and fairly useless without some customisation. Do you have usage stats on them? I imagine they are very low.

Even Atlassian support thought that the rules that the buttons create were editable.

Please fix this. 

This feature would unlock so much potential for our templates, and allow us to make sure certain steps are always performed when releasing new software to clients. Right now, the testers and product owners have to click the page and select the right automation whenever they need to do the things we have automated for them, which is easy to forget and feels like a hassle. So, every werek someone forgets something. A big, visual button is hard to miss, though. Please consider raising the priority of this suggestion! 🙏

I have created some custom automation rules in Confluence and then realised that I cant link them to a smart button. This would be really useful for me and my colleagues

The smart button functionality is very limited and greatly reduced in value compared to being able to trigger custom automations. The feature feels under-cooked. I can only hope the current implementation wasn't considered the end game for the smart button

That would help immensely our team we could use that to create Jira templates that would be filled through automation so that we gather the right information on any type of requests without creating multiple issue types. Since the feature by itself is already present, it doesn't seem like a lot of effort for the usage that it would gather.