Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node interacts with the Basecamp API to retrieve a list of projects. Specifically, the "Get All Projects" operation fetches all projects associated with the authenticated Basecamp account. It is useful for scenarios where you need to display, analyze, or process project data from Basecamp within an n8n workflow. For example, you might use this node to generate reports on active projects, archive old projects automatically, or synchronize project lists with other tools.
Properties
| Name | Meaning |
|---|---|
| Status | Filter projects by their status. Possible values are: active, archived, or trashed. |
Output
The node outputs JSON data representing the list of projects retrieved from Basecamp. Each item in the output corresponds to a project object containing details such as project ID, name, status, and other metadata provided by the Basecamp API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to projects, but this node focuses on JSON project data only.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the Basecamp account ID from credentials.
- No additional external dependencies beyond the Basecamp API and its authentication.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired API credentials.
- Network connectivity problems preventing access to the Basecamp API.
- Incorrect status filter values causing empty results or errors.
Error messages:
- Unauthorized or 401 errors indicate issues with the API key or OAuth token; re-authenticate or update credentials.
- 400 Bad Request errors may occur if the status filter value is invalid; ensure it is one of
active,archived, ortrashed. - Timeout or network errors suggest connectivity issues; verify internet access and Basecamp service status.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)