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 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 notifications 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 entries from. |
| Status | Filter to specify which schedule entries to retrieve; options are "Archived" or "Trashed". |
Output
The node outputs JSON data representing the schedule entries retrieved from the Basecamp API. Each entry corresponds to an individual schedule item matching the specified bucket, schedule, and status filters. The output structure typically includes details such as entry IDs, titles, statuses, timestamps, and other metadata provided by the Basecamp API.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the Basecamp API.
- Needs the Basecamp account ID (used internally to construct the API base URL).
- The node depends on the Basecamp API being accessible and the user having appropriate permissions to read schedule entries.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect bucket or schedule IDs may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid or expired API tokens; re-authenticate or update credentials.
- "Not Found" or similar errors suggest incorrect bucket or schedule IDs; verify these values.
- Rate limiting or API quota exceeded errors require waiting or adjusting usage patterns.