Overview
This node, named "Basecamp Sender," is designed to send messages to a specific message board within a Basecamp project. It is useful for automating communication workflows by programmatically posting messages to Basecamp message boards. Typical scenarios include notifying teams about updates, logging events, or integrating Basecamp messaging into broader automation pipelines.
For example, you could use this node to automatically post a status update or alert to a project’s message board whenever a certain event occurs in another system, such as a new support ticket or deployment notification.
Properties
| Name | Meaning |
|---|---|
| Account ID | The identifier of the Basecamp account where the project resides. |
| Project ID | The identifier of the specific Basecamp project containing the message board. |
| MessageBoard ID | The identifier of the message board within the project where the message will be posted. |
| Subject | The subject line or title of the message to be sent. |
| Content | The main body content of the message. Supports multiline text input. |
| Options | A collection of optional settings: |
| - Status | The status of the message; defaults to "active". |
| - Basecamp URL | The base URL for the Basecamp API; defaults to https://3.basecampapi.com. |
| - Token URL | The URL used to refresh OAuth tokens; defaults to https://launchpad.37signals.com. |
| - Put Response in Field | The name of the output field where the API response will be stored; defaults to "response". |
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains a JSON object with a field (default name "response", configurable) that holds the full response data returned from the Basecamp API after posting the message. This response includes details about the created message on the message board.
No binary data output is produced by this node.
Dependencies
- Requires an OAuth2-based API authentication token credential for Basecamp.
- Uses Axios HTTP client library internally to make REST API calls.
- Needs valid OAuth credentials with a refresh token to obtain access tokens dynamically.
- Requires network access to Basecamp API endpoints (
basecamp_url) and token refresh endpoint (token_url).
Troubleshooting
- Missing Refresh Token: If the OAuth credentials do not contain a refresh token, the node throws an error indicating no refresh token is available. Ensure your Basecamp OAuth credentials include a valid refresh token.
- Invalid IDs: Providing incorrect Account ID, Project ID, or MessageBoard ID will cause API errors. Double-check these identifiers.
- API Endpoint Issues: Customizing the Basecamp or token URLs incorrectly may lead to connection failures. Use default URLs unless you have a specific reason to change them.
- Permission Errors: Insufficient permissions in the Basecamp account or OAuth scopes can cause authorization failures.
- Network Errors: Connectivity issues or Basecamp service outages will prevent message posting.