Basecamp icon

Basecamp

Interact with Basecamp API
Join our community

Actions119

Overview

This node interacts with the Basecamp API to unarchive a specific recording within a project. It is useful when you want to restore access to recordings that were previously archived, making them active and accessible again in your Basecamp project workspace.

Common scenarios include:

  • Recovering important meeting or event recordings that were archived by mistake.
  • Managing project resources by toggling the archive status of recordings without deleting them.
  • Automating workflows where recordings need to be unarchived based on certain triggers or conditions.

For example, if a team member needs to review an old recorded discussion that was archived, this node can programmatically unarchive that recording so it becomes available for playback or further processing.

Properties

Name Meaning
Project ID The ID of the project (bucket) where the recording resides; used in the API endpoint path.
Recording ID The ID of the recording to unarchive; used in the API endpoint path.
Return Full Response Whether to return the full HTTP response including status code, headers, and body, or just the body.

Output

The node outputs JSON data representing the response from the Basecamp API after attempting to unarchive the specified recording. This typically includes details about the recording's new state (unarchived).

If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing:

  • Status code
  • Headers
  • Body (the main JSON content)

Otherwise, only the body of the response (the JSON data about the recording) is returned.

No binary data output is involved in this operation.

Dependencies

  • Requires an API authentication token configured in n8n credentials to authorize requests to the Basecamp API.
  • The node uses the Basecamp API base URL constructed with the account ID from credentials.
  • Proper permissions on the Basecamp account are necessary to modify recording states.

Troubleshooting

  • Invalid Project or Recording ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 Not Found error. Verify the IDs before running the node.
  • Insufficient Permissions: If the API token lacks rights to modify recordings, expect authorization errors (e.g., 403 Forbidden). Ensure the API key has appropriate scopes.
  • Network Issues: Connectivity problems may cause request failures. Check network settings and Basecamp service status.
  • Return Full Response Confusion: Enabling "Return Full Response" changes the output format. If subsequent nodes expect only JSON body, this might cause issues. Adjust downstream nodes accordingly.

Links and References

Discussion