Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node interacts with the Basecamp API to retrieve information about email forwards associated with a specific inbox within a project (referred to as a "bucket"). The "Get Forwards" operation fetches all forwarding rules configured for a given inbox, which can be useful for managing or auditing email routing settings in Basecamp projects.
Practical examples include:
- Automatically retrieving and listing all email forwards set up for a project inbox to display or process them further.
- Integrating with other workflows that need to analyze or modify forwarding rules based on project or inbox context.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The ID of the bucket (project) to query forwards from. Must be a number. |
| Inbox Id | The ID of the inbox within the bucket whose forwards are to be retrieved. Must be a number. |
Output
The node outputs JSON data representing the list of forwards associated with the specified inbox. Each forward typically includes details such as the forwarding address, status, and any related metadata defined by the Basecamp API.
If the node supports binary data output, it is not indicated here; the primary output is structured JSON data reflecting the forwards.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node depends on the Basecamp API endpoint for fetching forwards, which requires proper permissions and valid project and inbox IDs.
- No additional external services or environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Bucket or Inbox ID: If the provided bucket or inbox ID does not exist or the user lacks access, the API may return errors or empty results. Verify IDs and permissions.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- API Rate Limits: Excessive requests might trigger rate limiting by Basecamp. Implement retry logic or reduce request frequency if needed.
- Empty Results: If no forwards are configured for the specified inbox, the output will be empty. Confirm forwards exist before querying.
Links and References
- Basecamp API Documentation – Official documentation for Basecamp API endpoints and usage.
- n8n Documentation – General guidance on using n8n nodes and configuring credentials.