Confluence Cloud connector UpdatePage action fails with "id: must not be null"

Q&A
, ,
1

Environment:

  • Amazon Quick Desktop (macOS)
  • Atlassian Confluence Cloud connector (Quick Suite)

Steps to Reproduce:

  1. Connect the Atlassian Confluence Cloud connector
  2. Confirm read access works — call GetPageById with a valid page ID (e.g. 123456) → succeeds, returns page content and version info
  3. Call UpdatePage with:
    • id: 123456 (integer)
    • id_string: "123456" (string)
    • status: "current"
    • title: "Title" (matching existing title)
    • version: {"number": 5, "message": "test update"}
    • body: {"storage": {"representation": "storage", "value": "<p>Test content</p>"}}

Expected Behavior: Page updates successfully with new content at version 5.

Actual Behavior: Returns 400 with:

{"errors":[{"status":400,"code":"INVALID_REQUEST_BODY","title":"id: must not be null","detail":null}]}

Analysis:
The error originates from Atlassian’s API validation — meaning the request reaches Confluence and authenticates, but the id field is missing from the JSON request body. Confluence’s v2 PUT /pages/{id} endpoint requires id in both the URL path and the request body. The connector appears to route the id parameter to the URL path correctly but does not include it in the serialized body payload.

Evidence:

  • The same id value works for GetPageById (GET request, ID only needed in path)
  • The error is body validation, not auth (would be 403) or not-found (would be 404)
  • Tested with minimal content (<p>Test content</p>) — same result, ruling out body content issues
  • Tested multiple parameter combinations — always the same error

Impact:
UpdatePage is completely non-functional. No page can be updated through the connector regardless of content, permissions, or parameter formatting.

2

I ran into this same issue a couple weeks ago and submitted an AWS Support ticket. I’ve found this error primarily occurs on Quick Desktop and have been mostly successful using UpdatePage in the Quick web UI. AWS told me they are aware of the issue and are working on it. Here is the last response I received:

*Root Cause Identified

We’ve identified the root cause of the problem you’ve been experiencing. When the UpdatePage action runs in the Amazon Quick desktop app, the Confluence page ID is not being included in the update request body. The Confluence Cloud v2 API requires the ID in that body, so it rejects the request with the “id: must not be null” error.

I want to assure you that this is a defect in the desktop app’s request handling—not a problem with your connector configuration, credentials, or the ID values you supplied. You did everything correctly on your end.

Workaround

Until the fix is released, please use the following workaround:
Run the Confluence UpdatePage action from Amazon Quick on the web, where the request is formed correctly and the update succeeds. Creating Confluence pages from the desktop app is unaffected and can continue to be used.*

Timeline

Our development team is actively working on a fix for this issue. However, at this time, we do not have a specific ETA for when the fix will be publicly available. While I cannot provide an exact timeline for when this will be resolved, I will recommend to kindly follow the below AWS pages:
[+] What’s New at AWS – Cloud Innovation & News
[+] Announcements | AWS News Blog*

3

thank you for your quick reply ryan!

4

Hi @kellen.freeman,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.

5

“Don’t use the tool we have” did function, but is not a solution to the problem and I do not consider this resolved. The bug persists in the Amazon Quick native mac app.