Basecamp icon

Basecamp

Interact with Basecamp API

Actions119

Schedule Entry → Get Schedule Entries

AI-generated

Overview

This node operation retrieves schedule entries from a specified project (bucket) and schedule within the Basecamp API. It allows filtering entries by their status (e.g., upcoming) and supports pagination to return all results or a limited set. This is useful for workflows that need to access and process schedule data, such as project management automation, reporting upcoming tasks, or syncing schedule entries with other systems.

Use Case Examples

  1. Retrieve all upcoming schedule entries for a specific project and schedule to generate a report of upcoming tasks.
  2. Fetch schedule entries filtered by status to trigger notifications or reminders for upcoming events.

Properties

Name Meaning
Project ID The ID of the project (bucket) used in the API endpoint path to specify which project's schedule entries to retrieve.
Schedule ID The ID of the schedule used in the API endpoint path to specify which schedule's entries to retrieve.
Status Filter schedule entries by their status, such as 'upcoming', to narrow down the results.
Return All Results Boolean flag to determine whether to return all schedule entries or limit the results to a certain number.
Return Full Response Boolean flag to decide whether to return the full HTTP response including status code, headers, and body, or just the response body.

Output

JSON

  • statusCode - HTTP status code of the API response when full response is requested.
  • headers - HTTP headers of the API response when full response is requested.
  • body - The main content of the API response containing the schedule entries data.

Dependencies

  • Basecamp API with OAuth2 authentication

Troubleshooting

  • Ensure that the Project ID and Schedule ID are correct and correspond to existing resources in Basecamp to avoid 404 errors.
  • If filtering by status returns no results, verify that the status value is valid and that there are schedule entries matching that status.
  • When using pagination, ensure the API rate limits are respected to avoid throttling errors.
  • If 'Return Full Response' is enabled, be prepared to handle the full HTTP response structure in downstream nodes or workflows.

Discussion