Confluence Cloud icon

Confluence Cloud

Access to the Confluence Cloud REST API - Auto-generated from OpenAPI

Actions43

Overview

The "Create Page" operation in the Confluence Cloud node allows users to create a new page within a specified Confluence space. Pages are created as published by default unless explicitly marked as drafts. This operation is useful for automating content creation workflows, such as generating documentation pages, project notes, or knowledge base articles directly from other systems or triggers.

Practical examples include:

  • Automatically creating meeting notes pages after calendar events.
  • Generating product documentation pages from issue tracking systems.
  • Creating draft pages for review before publishing.

Properties

Name Meaning
Additional Fields Optional flags to modify page creation behavior:
- Embedded: Tag the content as embedded; content will be created in NCS. (Boolean)
- Private: Make the page private so only the creator can view and edit it. (Boolean)
- Root Level: Create the page at the root level of the space, outside the homepage tree. (Boolean)
Request Body JSON object representing the request body data for the page creation. This includes all necessary fields like title, space key, body content, parentId, status, etc.

Output

The output of this operation is the JSON response from the Confluence Cloud API representing the newly created page. This typically includes details such as:

  • The unique ID of the page.
  • Title and status (published or draft).
  • Space information where the page was created.
  • Metadata about the page version and permissions.
  • Links to access or edit the page.

No binary data is involved in this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the Confluence Cloud REST API.
  • The node uses the base URL provided by the user's Confluence domain credential.
  • Permissions required on the Confluence site:
    • Permission to view the target space.
    • Permission to create pages within that space.

Troubleshooting

  • Common Issues:

    • Insufficient permissions: Ensure the API token user has rights to create pages in the target space.
    • Invalid JSON in Request Body: The requestBody property must contain valid JSON; otherwise, parsing errors occur.
    • Conflicting parameters: If root-level is true, do not supply a parentId in the request body.

  • Error Messages:

    • 401 Unauthorized: Check API credentials and permissions.
    • 400 Bad Request: Verify the JSON structure in the request body and required fields like title.
    • 403 Forbidden: The user lacks permission to create pages in the specified space.

Resolving these usually involves verifying credentials, permissions, and ensuring the request body is correctly formatted.

Links and References

Discussion