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 schedule entries from a specified project bucket and schedule. It is useful for workflows that need to fetch archived or trashed schedule entries for reporting, auditing, or further processing within n8n. For example, you might use it to gather all archived tasks from a particular schedule to generate a summary report or to trigger follow-up actions based on past schedule entries.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the project bucket containing the schedule entries to retrieve. |
| Schedule Id | The numeric identifier of the specific schedule within the bucket to query. |
| Status | Filter to specify which schedule entries to retrieve: either "Archived" or "Trashed". |
Output
The node outputs JSON data representing the schedule entries matching the specified bucket, schedule, and status filters. Each entry in the output contains details as returned by the Basecamp API for schedule entries, such as entry content, timestamps, and metadata. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the user's Basecamp account ID.
- No additional external dependencies are indicated beyond the Basecamp API access.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Schedule Id will result in errors or empty results.
- Incorrect API credentials or insufficient permissions can cause authentication failures.
- Filtering by status requires valid values ("archived" or "trashed"); invalid values may cause request errors.
Error messages:
- Authentication errors typically indicate problems with the provided API key or OAuth token; verify credentials.
- HTTP 404 errors may mean the specified bucket or schedule does not exist or is inaccessible.
- Validation errors if required parameters (Bucket Id, Schedule Id) are missing.