Skip to main content
The Confluence Get child pages action lists all direct child pages under a specified parent page. Use it when you want an agent to understand or operate on a page subtree, such as reviewing related documentation, building navigation, or updating a group of related pages. This read-only action returns a paginated list of child pages that you can pass into follow-up actions. The action respects Confluence permissions and only returns child pages the connected account can view.

​
Limitations

  • The action lists only direct child pages for the specified parent. To traverse deeper descendants, you need to call the action again for each child page.

​
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 view pages in the target space.

​
Supported parameters

ParameterTypeDescription
Page IDStringRequired. Unique identifier used to target or filter a specific resource.
Page LimitIntegerMaximum number of results to return per page. Defaults to 25.
StartIntegerIndex of the first item to return (pagination offset).

​
Usage example

You want to review all documentation pages under a main product guide to ensure they are up to date. Instruction to an agent: “List all the child pages under the Product Guide Overview page in the Engineering space. For each child page, show me the title and last modified date so I can identify which ones need updating.” Resulting behavior:
  • Calls the Get child pages action with:
    • Page ID set to the Product Guide Overview page ID.
    • Returns a list of all direct child pages with their titles, IDs, and metadata.
    • The agent can then display this information or use it in follow-up actions like updating outdated pages.
Workflow tip: If you do not know the parent page ID, first use the Get pages action to search by title or label in the space. For parents with many children, use the limit and start parameters to paginate through results.

​
Troubleshooting

  • Possible cause: The parent page may not have any child pages, the connected account may not have permission to view them, or the ID may refer to a non-page content type such as a blog post that does not support a hierarchy.
  • Fix: Confirm that the ID you pass belongs to a page and that the connected account can see the same child pages directly in Confluence. If you expect more results, try broadening any filtering that happens earlier in your flow, for example, in a preceding Get pages call.
  • Possible cause: The Confluence action pack may not be fully configured, the connected account is missing, inactive, expired, or lacks the required scopes to read pages in the target space.
  • Fix: Ask an admin to verify that the Confluence action pack is enabled for your deployment. Have the user reconnect their Confluence account to refresh the token and ensure it has the right scopes.

​
FAQs

Get child pages lists direct children of a specific parent page ID, maintaining hierarchical relationships. Get pages retrieves a flat, paginated list of pages in a space with filters such as author, label, and status.