Basecamp icon

Basecamp

Interact with Basecamp API

Actions119

Overview

This node interacts with the Basecamp API to retrieve a specific occurrence of a schedule entry within a project. It is useful when you need detailed information about a particular scheduled event instance on a given date in a Basecamp project. For example, you might use this node to fetch details about a meeting or deadline occurrence for project tracking or automation purposes.

Properties

Name Meaning
Project ID The numeric ID of the project (bucket) where the schedule entry exists; used in the API path.
entryId The numeric ID of the schedule entry to retrieve; used in the API path.
Date The date (in YYYY-MM-DD format) of the specific occurrence of the schedule entry.
Return Full Response Boolean flag indicating whether to return the full HTTP response (status, headers, body) or just the response body.

Output

The node outputs JSON data representing the details of the requested schedule entry occurrence. This includes all relevant fields returned by the Basecamp API for that occurrence, such as timing, description, and status. If "Return Full Response" is enabled, the output will include the entire HTTP response object, including status code and headers, which can be useful for debugging or advanced workflows.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Basecamp API using OAuth2 authentication.
  • The node expects the user to provide valid project and schedule entry IDs along with the occurrence date.
  • Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

  • Invalid IDs or Date Format: Ensure that the Project ID, entryId, and Date are correctly specified. The date must follow the YYYY-MM-DD format exactly.
  • Authentication Errors: Verify that the API credentials are valid and have sufficient permissions to access the project and schedule entries.
  • Not Found Errors: If the schedule entry or occurrence does not exist, the API may return a 404 error. Double-check the IDs and date.
  • Full Response Usage: When enabling "Return Full Response," ensure downstream nodes can handle the full HTTP response structure.

Links and References

Discussion