Actions76
- 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
Overview
This node interacts with the Basecamp API to retrieve information about "forwards" within a specified project and inbox. Specifically, the "Get Forwards" operation fetches all forward entries associated with a given project (referred to as a bucket) and inbox.
Common scenarios where this node is beneficial include:
- Automating the retrieval of forwarded messages or items in a Basecamp project inbox for further processing or reporting.
- Integrating Basecamp forwards into other workflows, such as notifications, analytics, or archival systems.
- Synchronizing forward data from Basecamp with external databases or CRMs.
For example, a user might use this node to pull all forwards from a particular project inbox to analyze communication flow or to trigger follow-up actions based on forwarded content.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket). Used in the API endpoint path to specify which project to query. |
| Inbox ID | The ID of the inbox within the project. Used in the API endpoint path to specify which inbox. |
| Return All Results | Boolean option to return all available results by paginating through the API, or limit to a set number. |
| Return Full Response | Boolean option to return the full HTTP response including status code and headers instead of just the response body. |
Output
The node outputs JSON data representing the list of forwards retrieved from the specified project inbox. The structure typically includes an array of forward objects, each containing details about individual forwards such as sender, recipient, message content, timestamps, and related metadata.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, encompassing status code, headers, and body.
The 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 inboxes.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies are required beyond the Basecamp API and valid credentials.
Troubleshooting
- Invalid Project or Inbox ID: If the provided project or inbox ID does not exist or the authenticated user lacks access, the API may return errors such as 404 Not Found or 403 Forbidden. Verify IDs and permissions.
- Authentication Errors: Missing or expired OAuth2 tokens will cause authentication failures. Ensure credentials are correctly set up and refreshed.
- Pagination Issues: When "Return All Results" is enabled, pagination relies on HTTP Link headers. If the API changes pagination behavior, the node might fail to retrieve all data.
- API Rate Limits: Excessive requests may lead to rate limiting by Basecamp. Implement retry logic or reduce request frequency if encountering 429 Too Many Requests errors.
Links and References
- Basecamp API Documentation
- Basecamp Forward Resource API Reference (general reference for forwards endpoints)