Basecamp icon

Basecamp

Interact with Basecamp API

Actions76

Overview

This node allows users to create a new message type within a specified project in Basecamp. Message types are customizable categories or labels that help organize and classify messages in Basecamp projects. This operation is useful when you want to define specific message types with unique names and emoji icons to better structure communication within your projects.

Practical examples include:

  • Creating a "Bug Report" message type with a bug emoji for tracking issues.
  • Defining a "Feature Request" message type with a lightbulb emoji to highlight new ideas.
  • Adding a "Meeting Notes" message type with a notebook emoji to categorize meeting summaries.

Properties

Name Meaning
Project ID The numeric ID of the project (bucket) where the message type will be created.
Name The name of the message type to create (e.g., "Bug Report", "Feature Request").
Icon The emoji icon representing the message type (e.g., 🐞, 💡).
Return Full Response Whether to return the full HTTP response including status code and headers instead of just the response body.

Output

The node outputs JSON data representing the newly created message type as returned by the Basecamp API. This typically includes details such as the message type's ID, name, icon, and associated project information.

If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, containing status code, headers, and body.

No binary data is produced by this node.

Dependencies

  • Requires an active connection to the Basecamp API using OAuth2 authentication.
  • The user must provide valid credentials with access rights to the target Basecamp account and project.
  • The node uses the Basecamp API endpoint structured as https://3.basecampapi.com/{accountId}/buckets/{projectId}/message_types.json to create the message type.

Troubleshooting

  • Invalid Project ID: If the provided project ID does not exist or the authenticated user lacks access, the API will return an error. Verify the project ID and permissions.
  • Missing Required Fields: Ensure that both the "Name" and "Icon" fields are provided; otherwise, the API will reject the request.
  • Authentication Errors: If the OAuth2 token is expired or invalid, re-authenticate the credentials.
  • API Rate Limits: Excessive requests may lead to rate limiting; handle retries accordingly.

Common error messages:

  • 404 Not Found: Project ID is incorrect or inaccessible.
  • 401 Unauthorized: Authentication failure.
  • 422 Unprocessable Entity: Validation errors such as missing or invalid name/icon.

Links and References

Discussion