Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node operation retrieves detailed information about a specific "forward" entity within a given bucket (project) in the Basecamp system. It is useful when you need to fetch and work with data related to a particular forward, such as for reporting, auditing, or further processing in an automation workflow.
Practical examples include:
- Automatically fetching details of a forward after it has been created elsewhere.
- Integrating forward data into custom dashboards or notifications.
- Using forward information to trigger subsequent actions based on its properties.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The ID of the bucket (project) where the forward exists. This identifies the project context. |
| Forward Id | The unique ID of the forward to retrieve. |
Output
The output JSON contains the full details of the requested forward object as returned by the Basecamp API. This typically includes all metadata and attributes associated with that forward, such as IDs, timestamps, status, and any other relevant fields defined by the API.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the authenticated user's Basecamp account ID.
- Network access to the Basecamp API service is necessary.
Troubleshooting
- Invalid Bucket Id or Forward Id: If either ID is incorrect or does not exist, the API will return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Network Issues: Connectivity problems can lead to timeouts or failed requests. Check network settings and Basecamp service status.
- Permission Denied: Insufficient permissions for the provided credentials may result in authorization errors. Confirm that the API user has access rights to the specified bucket and forward.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)