Basecamp icon

Basecamp

Interact with Basecamp API

Actions119

Overview

This node interacts with the Basecamp API to manage templates within a Basecamp account. Specifically, the "Trash a Template" operation allows users to move a specified template to the trash (soft delete it). This is useful for cleaning up unused or outdated templates without permanently deleting them immediately.

Common scenarios include:

  • Archiving templates that are no longer needed but might be restored later.
  • Managing template lifecycle in project management workflows.
  • Automating cleanup of templates based on certain criteria.

Example: Automatically trashing templates older than a certain date as part of a maintenance workflow.

Properties

Name Meaning
templateId The numeric ID of the template to be trashed. Used in the API endpoint path.
Return Full Response Whether to return the full HTTP response including status code and headers, or just the body.

Output

The node outputs JSON data representing the response from the Basecamp API after attempting to trash the specified template. If "Return Full Response" is enabled, the output includes the full HTTP response object (status code, headers, and body). Otherwise, only the response body is returned.

No binary data output is involved in this operation.

Dependencies

  • Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
  • The node expects the Basecamp account ID to be configured in the credentials to construct the API base URL.
  • No additional external dependencies beyond the Basecamp API and proper authentication.

Troubleshooting

  • Invalid templateId: If the provided template ID does not exist or is incorrect, the API will likely return a 404 error. Verify the template ID before running the node.
  • Authentication errors: Ensure the OAuth2 credentials are valid and have sufficient permissions to modify templates.
  • API rate limits: Frequent calls may hit Basecamp API rate limits; handle such errors by adding retries or delays.
  • Return Full Response confusion: If enabled, the output structure changes; downstream nodes must handle the full HTTP response object accordingly.

Links and References

Discussion