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
This node interacts with the Basecamp API to retrieve details of a specific schedule entry within a project. It is useful when you want to fetch information about a particular event or appointment scheduled in a Basecamp project, such as meeting times, deadlines, or reminders.
Typical use cases include:
- Automating retrieval of schedule entries for reporting or synchronization with other calendar systems.
- Fetching detailed information about a schedule entry to trigger subsequent workflow steps based on its content.
- Integrating Basecamp schedule data into dashboards or notifications.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the schedule entry exists. Used in the API path. |
| Entry ID | The numeric ID of the specific schedule entry to retrieve. Used in the API path. |
| Return Full Response | Boolean option to return the entire HTTP response including status code and headers instead of just the body. |
Output
The node outputs JSON data representing the schedule entry retrieved from Basecamp. This includes all details provided by the Basecamp API for that entry, such as title, description, start and end times, and any other metadata associated with the schedule entry.
If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing status code, headers, and body, allowing advanced handling of the API response.
No binary data output is involved.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and schedule entry IDs.
- The Basecamp account ID must be configured in the credentials to construct the API endpoint URL.
Troubleshooting
- Invalid Project or Entry ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 error. Verify the IDs before running the node.
- Authentication Errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to access schedule entries.
- API Rate Limits: Frequent requests may hit Basecamp's rate limits; handle errors gracefully and consider adding delays or retries.
- Return Full Response Misuse: Enabling "Return Full Response" changes the output format; downstream nodes expecting only the body might fail. Use this option only if you need full HTTP details.