Hi!
This is more of a suggestion than a question, as I could not find support for this anywhere.
Please see Rovo's summary below. The use case stated is what we need to have a fully automated process. I imagine this could be useful for anyone creating recurring documentation in Confluence, like reports and meeting minutes etc based on templates without having to rely on building the page with markdown in the page content field.
Note: The smart values listed are Rovo's suggestions based on the conversation we had, so I can't guarantee their accuracy,
Component
Confluence Integration
Description
Problem:
When using the "Publish new page in Confluence" action in Jira Automation, only two smart values are available from the created page: {{createdPage.title}} and {{createdPage.url}}. There is no way to reference the page ID or body content in subsequent actions.
This means it is impossible to programmatically edit a page created by a previous automation step — for example, to populate dynamic values (dates, week numbers, metadata) into a page that was created from a Confluence template.
Current workaround limitations:
The "Edit page in Confluence" action only allows selecting an existing, static page from a dropdown — it cannot reference a dynamically created page from the flow
The "Page content" field is disabled when a template is selected in "Publish new page", so smart values cannot be injected into template-based pages
Confluence templates themselves do not support smart values or dynamic content
Using "Send web request" to call the Confluence API requires createdPage.id, which is not exposed
Requested enhancement:
Expose additional smart values from the "Publish new page" action:
{{createdPage.id}} — the numeric page ID
{{createdPage.body}} — the page body content (storage format)
{{createdPage.spaceKey}} — the space key
Allow the "Edit page in Confluence" action to accept "Current page in flow" or a smart value reference, not just a static page selection
Use case:
We run a weekly management status report. Automation creates a new Confluence page from a template every Monday with a dynamic title ({{now.year}} W{{now.weekOfYear}} - Status Updates). We need to also populate the date range field in the report metadata table — but there is currently no way to modify the created page after it's been published by the automation rule.
This forces a manual step every week for what should be a fully automated workflow.
Expected behavior:
After "Publish new page in Confluence" runs, subsequent actions should be able to reference and modify the created page using smart values — just as issue-based actions can reference {{issue.key}} and {{issue.fields}}.
