Limitations
- The available sources do not specify rate limits, maximum page size, or guarantees around duplicate titles when you call the action multiple times.
-
The body field supports multiple Confluence body representations. For typical usage, only the
body.storage.valuefield should be set. Using other representations without providing all required subfields can lead to validation errors.
Prerequisites
- Glean action must be enabled for your instance and the Confluence action pack must be available.
- A connected Confluence account must exist for the user, with permission to create pages in the target space and under the chosen parent page (if provided). Otherwise, the action fails with a permission error.
Supported parameters
| Parameter | Type | Description |
|---|---|---|
| Body content | Object | Required. Content body of the page, including representation and value, for example, storage. |
| Parent ID | String | Identifier of the parent page under which this page will be created. |
| Space ID | String | Required. Identifier of the space where the page will be created. |
| Title | String | Required. Title of the page to create. |
| Content format | String | The representation format of the content. Must be ‘storage’. |
Usage example
You want to create a new API documentation page under an existing documentation parent page in your Engineering space. Instruction to an agent: “Create a new Confluence page in the Engineering space titled REST API v3.0 Documentation. Place it under the Technical Documentation parent page. Include an overview section explaining the new REST API endpoints, authentication methods, and rate limits. Format it with proper headings and a table of contents.” Resulting behavior:-
Creates a page in the Engineering space with:
-
Space IDset to the Engineering space ID. -
Titleset toREST API v3.0 Documentation. -
Parent IDset to the Technical Documentation page ID to create a hierarchical structure. -
Bodycontaining the agent-generated content with headings, lists, and tables in Confluence storage format.
-
Troubleshooting
No page created or you see 403/404 errors from Confluence
No page created or you see 403/404 errors from Confluence
- Possible cause: The space ID or parent page ID may be invalid, or the connected account does not have permission to create pages in that location.
- Fix: Use Get spaces and optionally Get pages to retrieve valid IDs, and confirm that the connected account can create a page in the same space directly in Confluence.
Errors mentioning expired or invalid tokens when running the action
Errors mentioning expired or invalid tokens when running the action
- Possible cause: The connected Confluence account token has expired or is no longer valid.
- Fix: Ask the user to reconnect their Confluence account for this Glean action and retry the action.
Authentication flow errors such as redirect or callback URL mismatch when connecting Confluence
Authentication flow errors such as redirect or callback URL mismatch when connecting Confluence
- Possible cause: The OAuth app configuration for Confluence is incorrect.
- Fix: Admins must verify that the authorization and callback URLs in the OAuth app match the values shown in the Confluence action pack setup screen.
Actions appear authenticated but Create page still fails to execute
Actions appear authenticated but Create page still fails to execute
- Possible cause: The connected account may be missing required scopes or the action pack is not fully configured.
- Fix: Confirm that a connected account exists for this action pack, that it has the scopes required to create pages, and that the Confluence action pack is enabled for the deployment.
FAQs
Can this action update an existing page?
Can this action update an existing page?
No. Create page always creates a new page. To modify existing content, use the Update page action.
Does this action support rich formatting?
Does this action support rich formatting?
Yes. The action accepts content in Confluence storage representation, which preserves headings, lists, tables, and other formatting from the source document. When using an agent, simply describe the content structure in natural language and let the agent handle the conversion to storage format.