Actions80
- Todos Actions
- 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
Overview
The "Trash Template" operation in the Templates resource allows users to move a specific template to the trash (i.e., delete or archive it) within the Basecamp API context. This node is useful when you want to programmatically remove templates that are no longer needed, helping keep your template list clean and organized.
Practical examples include:
- Automatically cleaning up outdated templates as part of a scheduled workflow.
- Removing templates based on certain conditions or triggers in your automation process.
Properties
| Name | Meaning |
|---|---|
| Template Id | The unique numeric identifier of the template to be trashed. This property is required. |
Output
The node outputs JSON data representing the response from the Basecamp API after attempting to trash the specified template. This typically includes confirmation of the action or details about the trashed template. The exact structure depends on the API's response but generally confirms success or failure.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Template Id: Ensure the Template Id provided exists and is correct.
- Authentication errors: Verify that the API key or OAuth2 token is valid and has sufficient permissions.
- Network or API errors: Check connectivity and Basecamp API status.
Error messages:
- "Template not found" or similar indicates the Template Id does not exist.
- Authentication failures suggest invalid or expired credentials.
Resolving these usually involves verifying input parameters and refreshing or reconfiguring credentials.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)