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
Forwards → Get Forwards
AI-generatedOverview
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 retrieving and listing all email forwards set up for a particular inbox to display or process them further.
- Integrating with other workflows that need to verify or update forwarding rules based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The ID of the bucket (project) to query. |
| Inbox Id | The ID of the inbox whose forwards to get. |
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 provided by the Basecamp API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node depends on the Basecamp API being accessible and the user having appropriate permissions to read forwards for the specified bucket and inbox.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Inbox Id parameters will cause the request to fail.
- Authentication errors if the API key or OAuth token is invalid or expired.
- Permission errors if the authenticated user does not have access to the specified bucket or inbox.
- Network connectivity problems preventing access to the Basecamp API.
Error messages and resolutions:
- 401 Unauthorized: Check that the API credentials are correctly configured and valid.
- 404 Not Found: Verify that the Bucket Id and Inbox Id exist and are correct.
- 403 Forbidden: Ensure the authenticated user has permission to access the requested resources.
- Network errors: Confirm internet connectivity and Basecamp API availability.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API integrations)