# Forge Automation Actions is now generally available **URL:** \ **Category:** Adopting Forge from Connect\ **Tags:** automation, automation-rules, forge-action, forge\ **Created:** [December 8, 2025, 4:45am UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576 "2025-12-08T04:45:26Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![PrashantBabber](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@PrashantBabber](https://community.developer.atlassian.com/u/PrashantBabber)\ **Post date:** [December 8, 2025, 4:45am UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/1 "2025-12-08T04:45:26Z")
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 ## Get started **Documentation:** - [Build automations with Forge](https://developer.atlassian.com/platform/forge/building-automations/) - [Action module reference](https://developer.atlassian.com/platform/forge/manifest-reference/modules/automation-action/) ## From EAP to GA Thank you to the partners who participated in our Early Access Program and helped shape this feature with their valuable feedback. ## We want your feedback Have questions or feedback? Share your experiences in the comments below or reach out through the [Developer Community](https://community.developer.atlassian.com/). ---
**Author:** ![marc](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/marc/32/39047_2.png) [@marc](https://community.developer.atlassian.com/u/marc)\ **Post date:** [December 8, 2025, 10:03am UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/2 "2025-12-08T10:03:03Z")
Hi @PrashantBabber Great news. Is Confluence support also coming? ---
**Author:** ![sopel](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/sopel/32/48679_2.png) [@sopel](https://community.developer.atlassian.com/u/sopel)\ **Post date:** [December 8, 2025, 3:20pm UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/3 "2025-12-08T15:20:27Z")
Congrats @PrashantBabber 🎉 - one question/ask: > [@PrashantBabber](#): > > **Smart values output** — Forge actions can now output smart values, enabling seamless data flow between actions and dynamic automation workflows. This does not seem to be documented yet (even though the changelog stated [Forge Automation Actions is now in GA](https://developer.atlassian.com/platform/forge/changelog/#CHANGE-2937) as of 2025-12-01 already), to the contrary actually, see [A note on return values](https://developer.atlassian.com/platform/forge/manifest-reference/modules/automation-action/#a-note-on-return-values): > 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? ---
**Author:** ![sopel](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/sopel/32/48679_2.png) [@sopel](https://community.developer.atlassian.com/u/sopel)\ **Post date:** [December 10, 2025, 8:40pm UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/4 "2025-12-10T20:40:40Z")
@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](https://community.developer.atlassian.com/t/missing-forge-action-connection-spi/97654) topic for separation of concerns. ---
**Author:** ![Chris\_at\_DigitalRose](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/chris_at_digitalrose/32/41070_2.png) [@Chris\_at\_DigitalRose](https://community.developer.atlassian.com/u/Chris_at_DigitalRose)\ **Post date:** [December 10, 2025, 10:58pm UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/5 "2025-12-10T22:58:04Z")
@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](https://ecosystem.atlassian.net/browse/ROADMAP-121) ---
**Author:** ![PrashantBabber](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@PrashantBabber](https://community.developer.atlassian.com/u/PrashantBabber)\ **Post date:** [December 15, 2025, 9:39am UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/6 "2025-12-15T09:39:21Z")
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. ---
**Author:** ![PrashantBabber](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@PrashantBabber](https://community.developer.atlassian.com/u/PrashantBabber)\ **Post date:** [December 15, 2025, 9:42am UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/7 "2025-12-15T09:42:20Z")
> [@marc](#): > > Great news. Is Confluence support also coming? 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. ---
**Author:** ![sopel](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/sopel/32/48679_2.png) [@sopel](https://community.developer.atlassian.com/u/sopel)\ **Post date:** [December 20, 2025, 4:19pm UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/8 "2025-12-20T16:19:23Z")
> [@marc](#): > > Great news. Is Confluence support also coming? @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: 1. 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** 2. 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** 3. 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 4. ~~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~~ ) 5. 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). ---
**Author:** ![system](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/7/8/78672baa5ba80cd9164376457051d0eec038b082.png) [@system](https://community.developer.atlassian.com/u/system)\ **Post date:** [January 7, 2026, 4:46am UTC](https://community.developer.atlassian.com/t/forge-automation-actions-is-now-generally-available/97576/9 "2026-01-07T04:46:13Z")
Closed on January 7, 2026, 4:46am UTC This topic was automatically closed after 30 days. New replies are no longer allowed.