Unable to Select Confluence Space in Jira Automation "Publish New Page" Action

[cvanduyn]

I'm testing a Jira automation that runs on a schedule, invokes an AI agent, and then creates a Confluence page using the agent response as the page content.

The Confluence connection authenticates successfully and shows as Connected, but when I get to the Space dropdown in the Publish New Page In Confluence action, no spaces are available to select. I've tested this with multiple Jira spaces (projects) in the same Atlassian organization and Jira site, with the same result...

I've attached screenshots of:

1. The automation
2. The successful Confluence connection
3. The empty Space dropdown

Has anyone else run into this?

Is there a permission or configuration I'm missing, or could this be a bug related to some of the newer Atlassian Automation/AI features that have been rolling out?

[Davit Mkrtchyan - Be On Time]

Hi @cvanduyn!

This is a classic and quite frustrating scenario where "Connected" doesn't necessarily mean "Authorized."

In Atlassian's ecosystem, the Connected status in the automation settings usually confirms that the OAuth handshake or API token authentication was successful (i.e., the system knows who you are). However, the empty dropdown in the "Publish New Page" action is an authorization issue (i.e., the system doesn't think you have the right to do anything in those spaces).

Here is a checklist to narrow this down:

1. Verify Space-Level Permissions: Ensure that the exact account used to establish the connection has the 'Create Page' permission in the target Confluence spaces. If the user can't manually create a page in that space, the automation won't see it.

2. Test with a Space Admin: To rule out a bug in the AI agent/Automation flow, try creating a temporary connection using a Confluence Space Administrator account. If the spaces suddenly appear, you know it's a granular permission issue with the original account.

3. Global Permissions: Check if the account has the global permission to use Confluence. Sometimes, a user might have access to a space but lack the broader permission to interact with the Confluence API.

4. The "New Feature" Factor: Since you mentioned this involves the newer AI agent features, there might be a specific "App" or "Bot" user created in the background. Check the User Management in Confluence to see if any automation-related service accounts have been created and if they are added to the space permissions.

Pro Tip: If you have access to the browser's Developer Tools (Network tab), try clicking that dropdown and look for the API call to /wiki/rest/api/space. If you see a 403 Forbidden or an empty array [] in the response, it confirms that the API is rejecting the request based on permissions, not a connection failure.

Hope this helps you get those pages publishing! 🚀