Basecamp icon

Basecamp

Interact with Basecamp API

Actions76

Overview

The "Trash a Recording" operation in the Basecamp node allows users to move a specific recording within a project (referred to as a bucket) to the trash. This is useful for managing and cleaning up recordings that are no longer needed without permanently deleting them immediately. Typical scenarios include archiving outdated meeting recordings or removing erroneous audio files from a project workspace.

Properties

Name Meaning
Project ID The numeric identifier of the project (bucket) containing the recording.
Recording ID The numeric identifier of the recording to be trashed.
Return Full Response Option to return the complete API response including status code, headers, and body, or just the response body.

Output

The output JSON contains the response from the Basecamp API after attempting to trash the specified recording. If "Return Full Response" is set to false, only the response body is returned, typically confirming the success or failure of the trash action. If true, the output includes the full HTTP response details such as status code and headers along with the body.

No binary data is involved in this operation.

Dependencies

  • Requires an active connection to the Basecamp API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for API calls is constructed using the account ID from the credentials.

Troubleshooting

  • Invalid Project or Recording ID: Errors may occur if the provided IDs do not exist or the user lacks permission. Verify IDs and access rights.
  • Authentication Errors: Ensure the API key or OAuth token is valid and has sufficient scopes.
  • API Rate Limits: Frequent requests might hit rate limits; handle retries or backoff accordingly.
  • Return Full Response Misuse: Setting "Return Full Response" to true changes the output format; downstream nodes must handle this structure properly.

Links and References

Discussion