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 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 an inbox, which can be useful for managing or auditing email routing settings in Basecamp projects.
Practical examples include:
- Automatically listing all email forwards set up for a particular inbox to verify configurations.
- Integrating with other workflows that need to process or display forwarding rules.
- Auditing email forwards to ensure compliance or troubleshoot delivery issues.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The ID of the bucket (project) to query. |
| Inbox Id | The ID of the inbox whose forwards to get. |
Both properties are required and must be provided as numbers.
Output
The node outputs JSON data representing the list of forwards for the specified inbox. Each forward typically includes details such as the forwarding address, status, and any related metadata defined by the Basecamp API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API base URL constructed dynamically from the user's credentials.
- Proper configuration of the API authentication token or OAuth2 credentials is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Bucket Id or Inbox Id will cause the API request to fail.
- Authentication errors if the API key or OAuth2 token is not correctly configured.
- Network connectivity problems may prevent reaching the Basecamp API.
Error Messages:
- Unauthorized or 401 errors indicate invalid or expired credentials; re-authenticate or update credentials.
- 404 Not Found errors may mean the specified bucket or inbox does not exist or the user lacks access.
- Rate limiting errors require waiting before retrying or adjusting API usage.
Links and References
- Basecamp API Documentation
- n8n documentation on creating custom nodes