Actions35
- Space Actions
- Page Actions
- Template Actions
- Search Actions
- Comment Actions
- Get Page Footer Comments
- Get Page Inline Comments
- Get Blog Post Footer Comments
- Get Blog Post Inline Comments
- Get Custom Content Comments
- Get Footer Comments
- Create Footer Comment
- Get Footer Comment By Id
- Update Footer Comment
- Delete Footer Comment
- Get Footer Comment Children
- Get Inline Comments
- Create Inline Comment
- Get Inline Comment By Id
- Update Inline Comment
- Delete Inline Comment
- Get Inline Comment Children
Overview
The "Get Blueprint Templates" operation of the Confluence Cloud node retrieves blueprint templates from Confluence. Blueprint templates are predefined page templates provided by Confluence blueprints, which can be global or space-specific. This operation allows users to fetch all global blueprint templates or those within a specific space.
This node operation is useful when you want to:
- List available blueprint templates for creating new pages based on standard layouts.
- Automate documentation workflows by selecting appropriate blueprint templates programmatically.
- Integrate Confluence template data into other systems or processes.
Example use case:
A team automates their project documentation creation by fetching blueprint templates and then using them to create pages with consistent structure across multiple spaces.
Properties
Name | Meaning |
---|---|
Return All | Whether to return all blueprint templates or limit the number of results. |
Limit | Maximum number of blueprint templates to return (max 250). Only used if "Return All" is false. |
Additional Fields | Collection of optional fields: - Space Key: The key of the space to query for templates. If omitted, global blueprint templates are returned. - Expand: Properties of the template to expand. Options: body , body.storage (returns content in storage format). |
Output
The output JSON contains an array of blueprint templates under the property results
. Each item represents a blueprint template with its metadata and optionally expanded properties such as the template body content.
The structure typically includes:
- Template identifiers and names.
- Associated space information (if space-specific).
- Content details if expanded (
body
orbody.storage
). - Other metadata related to the blueprint template.
No binary data output is involved in this operation.
Dependencies
- Requires access to a Confluence Cloud instance with appropriate permissions.
- Requires an API authentication token configured in n8n credentials to authenticate requests.
- The node uses the Confluence REST API endpoint
/wiki/rest/api/template/blueprint
.
Troubleshooting
- Permission errors: Ensure the API user has 'View' permission for the target space to access space-specific blueprints, and 'Can use' global permission to access global blueprints.
- Empty results: Verify the
spaceKey
parameter if querying space-specific templates; if omitted, only global templates are returned. - Limit exceeded: The Confluence API limits results to 250 per request. Use "Return All" to paginate through all results.
- Invalid expand values: Only
body
andbody.storage
are valid expand options. Using unsupported values may cause errors or ignored parameters.
Links and References
- Confluence Cloud REST API - Blueprint Templates
- Confluence Blueprint Templates Documentation
- Confluence Query Language (CQL) (for related search operations)