Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node interacts with a template system to create a new project construction based on a specified template. It is useful in scenarios where users want to automate the creation of projects by applying predefined templates, ensuring consistency and saving time. For example, a project manager can use this node to quickly instantiate a construction project with all necessary settings and configurations derived from a chosen template.
Properties
| Name | Meaning |
|---|---|
| Template Id | The numeric identifier of the template to use for creating the project construction. |
| Project | A JSON object representing the project details to be created using the selected template. |
Output
The node outputs JSON data representing the result of the project construction creation. This typically includes information about the newly created project such as its ID, status, and any other relevant metadata returned by the API or service handling the template application. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential or OAuth2 token to authenticate requests to the external service managing templates and projects.
- The node uses HTTP requests with JSON payloads to communicate with the external API.
- Proper configuration of authentication credentials within n8n is necessary for successful operation.
Troubleshooting
- Common issues:
- Invalid or missing Template Id may cause the API to reject the request.
- Malformed JSON in the Project property can lead to parsing errors.
- Authentication failures if the API key or token is not set up correctly.
- Error messages:
- "Template not found" indicates the provided Template Id does not exist.
- "Invalid JSON body" suggests the Project JSON is incorrectly formatted.
- "Unauthorized" or "Authentication failed" means credentials need to be checked or refreshed.
- Resolutions:
- Verify the Template Id exists and is correct.
- Validate the JSON structure of the Project input before execution.
- Ensure API credentials are properly configured and have sufficient permissions.
Links and References
- Refer to the external API documentation for templates and project creation for detailed schema and examples.
- n8n documentation on how to configure credentials and handle JSON inputs.