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
The "Get Inbox" operation of the Inbox resource in this Basecamp node retrieves details about a specific inbox within a given project (referred to as a "bucket" in the API). This operation is useful when you want to fetch information or metadata about an inbox, such as its contents or status, within a particular project context.
Common scenarios include:
- Accessing messages or notifications grouped in an inbox for project management.
- Integrating Basecamp inbox data into workflows for monitoring or reporting.
- Automating retrieval of inbox details to trigger further actions based on inbox content.
For example, you might use this node to get the latest messages in a project's inbox and then process or forward them automatically.
Properties
Name | Meaning |
---|---|
Project ID | The numeric ID of the project (bucket) where the inbox resides. Used in the API endpoint path. |
Inbox ID | The numeric ID of the inbox to retrieve. Used in the API endpoint path. |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The output JSON contains the response from the Basecamp API for the specified inbox. By default, it returns only the body of the response, which includes the inbox details such as its properties and contained items.
If "Return Full Response" is enabled, the output will include the entire HTTP response object, including status code, headers, and body, allowing more detailed handling of the API response.
This node does not output binary data.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- Needs the Basecamp account ID to construct the API base URL.
- The node depends on the Basecamp API being accessible and the provided project and inbox IDs being valid.
Troubleshooting
- Invalid Project or Inbox ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 error. Verify that the IDs correspond to existing resources in your Basecamp account.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the OAuth2 credential is correctly set up and authorized.
- Permission Issues: Insufficient permissions for the authenticated user may result in authorization errors. Confirm that the API token has access to the specified project and inbox.
- Return Full Response Confusion: Enabling "Return Full Response" changes the output structure. Make sure downstream nodes handle the full response object accordingly.