Actions119
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
The "Get Schedule Entries" operation of the Schedule Entry resource in this Basecamp node retrieves entries from a specific schedule within a project (referred to as a bucket). This operation is useful for workflows that need to access scheduled events or tasks, such as fetching upcoming meetings, deadlines, or milestones associated with a project.
Typical use cases include:
- Automating reminders or notifications based on upcoming schedule entries.
- Integrating schedule data into other systems like calendars or reporting tools.
- Monitoring schedule changes or statuses programmatically.
For example, you could use this node to fetch all upcoming schedule entries for a project and send summary emails to team members automatically.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the schedule. Used in the API path. |
| Schedule ID | The numeric ID of the schedule to retrieve entries from. Used in the API path. |
| Status | Filter schedule entries by their status. Options include: upcoming (default), others may be supported by the API. |
| Return All Results | Boolean flag indicating whether to return all available results (true) or limit to a default page size (false). |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) instead of just the body. |
Output
The output JSON contains an array of schedule entry objects representing individual entries retrieved from the specified schedule. Each entry typically includes details such as title, description, start and end times, status, and other metadata defined by the Basecamp API.
If "Return Full Response" is enabled, the output will include the entire HTTP response object, including status code and headers, which can be useful for debugging or advanced handling.
This node does not output binary data.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to access projects and schedules.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies beyond the Basecamp API and n8n's OAuth2 credential setup.
Troubleshooting
- Invalid Project or Schedule ID: If the provided IDs do not exist or the authenticated user lacks access, the API will return errors. Verify IDs and permissions.
- Status Filter Issues: Using unsupported status values may result in empty responses or errors. Use valid status filters as per Basecamp API documentation.
- Pagination Handling: When "Return All Results" is false, only a limited number of entries are returned. Enable it to fetch all pages but be mindful of rate limits.
- Authentication Errors: Ensure the OAuth2 token is valid and has not expired. Re-authenticate if necessary.
- Full Response Usage: Enabling "Return Full Response" changes output structure; downstream nodes must handle this accordingly.