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; 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 provided bucket ID, schedule ID, and status filter. The structure typically includes details such as entry identifiers, titles, statuses, timestamps, and other metadata as defined by the Basecamp API response.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the Basecamp API.
- The node depends on the Basecamp API being accessible and the user having appropriate permissions to read schedule entries.
- No additional external dependencies beyond the Basecamp API and its authentication are required.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id or Schedule Id will result in errors or empty responses.
- Incorrect or expired API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid API tokens; re-authenticate or update credentials.
- "Not Found" errors may mean the specified bucket or schedule does not exist or the user lacks access.
- Rate limiting errors from the API require waiting before retrying requests.