We’re thrilled to announce that Forge Automation Actions has reached General Availability (GA)!
This feature allows you to extend the Atlassian Automation Platform by building custom Forge-based actions that integrate seamlessly with Jira automation rules.
What’s new in GA
Smart values output — Forge actions can now output smart values, enabling seamless data flow between actions and dynamic automation workflows.
What you can build
With Forge Automation Actions, you can:
Create custom actions that appear in the Automation rule builder
Build integrations with external tools (Jenkins, AWS, HubSpot, MS 365, and more)
Automate complex workflows that weren’t possible before
Distribute your automation actions through the Atlassian Marketplace
At this point, your action won’t be able to contribute any data back to Automation. Return values from your forge function will be ignored, unless you return a special errors object (see section below).
Can you arrange for the missing docs on the smart values SPI to be published as well?
@PrashantBabber – I’ve meanwhile identified another case of potentially missing docs for or implementation of an Automation action SPI that’s used by Atlassian’s own actions and have created the Missing Forge action connection SPI topic for separation of concerns.
@PrashantBabber This is a great step forward and adds value. Any forecast on the complementary capability where RoA apps can trigger automation rules? ROADMAP-121
Hello @sopel,
Thank you for highlighting this and for your attention to detail regarding the documentation. We will review this internally to ensure the necessary information is made available. Your feedback helps us improve the experience for everyone—thanks again for raising it.
Thank you for your interest and for sharing your feedback about Confluence support. We’re always looking to understand which integrations and features are most valuable to our users, and input like yours helps us shape our priorities. I’d be happy to connect if you have further feedback on Jira or specific requirements for Confluence—your insights are always appreciated.
@marc - based on some early tests and the fact that a Jira only restriction isn’t mentioned at all, I had been under the impression that the action already works in Confluence and was thus surprised by your question, so I’ve quickly rechecked (i.e. no full E2E test) via new apps created with Forge CLI 12.12.0, and the encountered behavior is both mostly promising yet slightly concerning irritating:
Creating a new app and installing it in Confluence first, the action shows up in Confluence spaces - however, when installing the same app in Jira afterwards, the action does not show up in Jira spaces in turn
Conversely, creating a new app and installing it in Jira first, the action shows up in Jira spaces - however, when installing the same app in Confluence afterwards, the action does not show up in Confluence spaces in turn
As a cross check, I’ve then change the action and actionProvider keys and action name in 2 and re-installed the app in Confluence, and suddenly the action showed up in both Jira and Confluence, albeit with a BETA flag in Confluence
Finally Oddly, I now have the same app installed in both Jira and Confluence as evidenced by the forge uninstall command, and it also shows up within ‘Connected apps’ twice with the same name as expected, but both installation details claim to be Jira (the overview is correct though, i.e. filtering for either Jira or Confluence only shows just one rather than two), i.e. there might be conflicting bugs in the ‘Connected apps’ and/or cross-app compatibility handling (still only in preview after all, and I haven’t yet tested this with cross-app compatibility enabled either)
Finally, I’ve now also created a new app with cross-app compatibility enabled (Jira required, Confluence optional), installed it in Jira and confirmed the action shows up, then also connected Confluence via the ‘Connected app’ UI, and confirmed the action shows up in both Jira and Confluence
So that has been a quick and dirty test with pretty fuzzy results and possible test errors (PEBKAC, eventually consistency, …), and I lack the time to investigate further right now, just wanted to convey that there’s already more Confluence support than meets the eye (matching the docs not mentioning any resp. restrictions at all).
- one question/ask: