Actions80
- 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
- Todos 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 supports filtering projects by their status, such as active, archived, or trashed. This node is useful for workflows that need to process or analyze project data from Basecamp, automate reporting, or synchronize project information with other systems.
Example use cases:
- Automatically fetching all active projects to generate status reports.
- Archiving project data in an external database.
- Triggering notifications based on project statuses.
Properties
| Name | Meaning |
|---|---|
| Status | Filter projects by their status. Possible values: active, archived, or trashed. If left empty, no status filter is applied and all projects are returned. |
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 as 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 authentication token configured via OAuth2 credentials for Basecamp.
- The node uses the Basecamp API endpoint constructed dynamically using the user's Basecamp account ID.
- No additional external dependencies beyond the Basecamp API and n8n's OAuth2 credential system.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication errors. Ensure the OAuth2 token is valid and refreshed.
- Incorrect Basecamp account ID configuration can lead to failed requests.
- Filtering by an unsupported status value may return no results or an error.
Error messages:
- Authentication failures: Check and reauthorize the API credentials.
- HTTP 404 or 403 errors: Verify the Basecamp account ID and permissions.
- Empty responses when filtering: Confirm the status filter value is correct (
active,archived, ortrashed).