Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
The "Create a Message" operation in the Message resource allows users to post a new message within a specific project and message board in Basecamp. This node is useful for automating communication workflows, such as sending announcements, updates, or notifications directly into Basecamp projects without manual intervention.
Typical use cases include:
- Automatically posting status updates from other systems into a Basecamp message board.
- Creating messages triggered by external events (e.g., new support tickets, completed tasks).
- Broadcasting information to team members subscribed to certain message boards.
Properties
Name | Meaning |
---|---|
Project ID | The numeric ID of the project (bucket) where the message will be posted. |
messageBoardId | The numeric ID of the message board within the project where the message will be created. |
Subject | The title or subject line of the message. |
Status | The publication status of the message; set to "active" to publish immediately. |
Content | The body content of the message, which may include HTML formatting. |
Category ID | Optional numeric ID representing the message type or category. |
Notification Recipients | Optional array of numeric IDs of people to notify about the new message (e.g., [2,3]). |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) instead of just the response body. |
Output
The node outputs JSON data representing the response from the Basecamp API after creating the message. By default, this includes the newly created message's details such as its ID, subject, content, status, and related metadata.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, containing status code, headers, and body, allowing for more detailed handling or debugging.
This node does not output binary data.
Dependencies
- Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
- The node expects the Basecamp account ID to be configured in the credentials to construct the API endpoint URL.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
- Invalid Project or Message Board ID: If the provided project or message board ID does not exist or the user lacks permissions, the API will return an error. Verify that the IDs are correct and accessible with the authenticated account.
- Missing Required Fields: The operation requires
Project ID
,messageBoardId
,Subject
, andStatus
. Omitting any of these will cause validation errors. - Status Value: The
Status
must be set to"active"
to publish immediately. Using other values may result in unexpected behavior or failure. - Notification Recipients Format: The
subscriptions
field must be a valid JSON array of numeric IDs. Incorrect formatting can cause request failures. - API Rate Limits: Frequent calls may hit Basecamp API rate limits, resulting in temporary errors. Implement retry logic or backoff if needed.
- Return Full Response Usage: Enabling this option changes the output format. Downstream nodes expecting only the message body might fail if they do not handle the full response structure.
Links and References
- Basecamp API Documentation - Messages
- Basecamp API Authentication
- n8n Documentation on HTTP Request Node (for understanding API interactions)