Actions43
- 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
- Label Actions
Overview
This node operation allows you to create a new content template in Confluence Cloud via its REST API. Content templates are reusable page structures or blueprints that help standardize and speed up the creation of pages within Confluence spaces or globally across the site. This operation is useful when you want to automate the creation of such templates programmatically, for example, to deploy standardized documentation templates or project plans.
Typical use cases include:
- Automating the setup of new project spaces with predefined page templates.
- Creating global templates for company-wide documentation standards.
- Managing templates as part of a CI/CD pipeline for documentation.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON data representing the content template to be created. This should conform to the Confluence API's expected structure for a content template. |
The "Request Body" property expects a JSON object describing the template details such as name, body content, space key (if applicable), and other relevant fields required by the Confluence API.
Example of a minimal request body might look like:
{
"name": "My Template",
"templateType": "page",
"body": {
"storage": {
"value": "<p>This is my template content</p>",
"representation": "storage"
}
},
"space": {
"key": "SPACEKEY"
}
}
Output
The output of this operation will be the JSON response from the Confluence API after creating the content template. This typically includes details about the newly created template such as its ID, name, type, body content, and associated space information.
The output JSON structure corresponds directly to the Confluence REST API's response for creating a content template, allowing further workflow steps to utilize the template ID or other metadata.
No binary data is involved in this operation.
Dependencies
- Requires an active connection to a Confluence Cloud instance.
- Requires an API authentication credential with sufficient permissions:
- 'Admin' permission on the target space to create a space template, or
- 'Confluence Administrator' global permission to create a global template.
- The node uses the Confluence Cloud REST API endpoint
/wiki/rest/api/templatewith HTTP POST method.
Troubleshooting
- Permission errors: If the API returns authorization errors, verify that the API token or credentials used have the necessary admin rights on the space or global level.
- Invalid JSON in Request Body: Ensure the JSON provided in the "Request Body" field is valid and matches the expected schema for a content template. Malformed JSON or missing required fields will cause API errors.
- API endpoint errors: Network issues or incorrect base URL configuration can cause failures. Confirm the domain and credentials are correctly set in the node configuration.
- Template conflicts: Attempting to create a template with a duplicate name or invalid parameters may result in API errors. Check the error message for details.