Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node integrates with the Basecamp API to perform various operations on Basecamp resources. Specifically, for the "Project" resource and the "Trash a Project" operation, it allows users to move a project to the trash (effectively deleting or archiving it). This is useful in scenarios where projects are no longer active or needed but you want to keep them retrievable from trash rather than permanently deleting immediately.
Practical examples include:
- Archiving completed client projects to keep your workspace clean.
- Removing test or demo projects created during setup or training.
- Managing project lifecycle by programmatically trashing projects based on business rules.
Properties
Name | Meaning |
---|---|
projectId | The numeric ID of the project to be trashed. Used in the API endpoint path. |
Return Full Response | Boolean option to return the full HTTP response including status code, headers, and body, instead of only the response body. |
Output
The node outputs JSON data representing the response from the Basecamp API after attempting to trash the specified project. If "Return Full Response" is enabled, the output includes the full HTTP response object (status code, headers, and body). Otherwise, it returns only the response body content.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests against the Basecamp API.
- The node uses the Basecamp API base URL constructed dynamically using the account ID from credentials.
- No additional external dependencies beyond the Basecamp API and proper OAuth2 or API key credentials.
Troubleshooting
Common issues:
- Invalid or missing
projectId
will cause the API call to fail; ensure the project ID exists and is correct. - Authentication errors if the API token or OAuth credentials are invalid or expired.
- Insufficient permissions to trash projects in the Basecamp account.
- Invalid or missing
Error messages:
- HTTP 404 Not Found: The specified project ID does not exist.
- HTTP 401 Unauthorized or 403 Forbidden: Authentication failed or user lacks permission.
- HTTP 400 Bad Request: Malformed request, possibly due to incorrect parameters.
To resolve these, verify the project ID, refresh or reconfigure credentials, and check user permissions in Basecamp.
Links and References
- Basecamp API Documentation – Official API docs for understanding endpoints and responses.
- n8n Documentation – For configuring credentials and using nodes effectively.