Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node allows you to create a new document within a specified vault and bucket in the Basecamp system. It is useful for automating the creation of project documentation, meeting notes, or any structured content that needs to be stored and shared within Basecamp. For example, you could use this node to automatically generate status reports or meeting summaries from other data sources and publish them directly into your Basecamp projects.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the document will be created. |
| Vault Id | Numeric identifier of the vault containing the bucket. |
| Title | The title of the document to be created. |
| Content | The body of the document in HTML format. Supports rich text with allowed HTML tags. |
| Status | Document status; currently only "Active" is supported, which publishes the document immediately. |
Output
The node outputs JSON data representing the newly created document as returned by the Basecamp API. This typically includes details such as the document ID, title, content, status, creation timestamps, and possibly URLs or references to the document within Basecamp. There is no binary output.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- The node uses the Basecamp API endpoint constructed dynamically using the authenticated user's Basecamp account ID.
- No additional environment variables are needed beyond the API credential setup.
Troubleshooting
- Invalid Bucket or Vault IDs: Ensure that the numeric IDs provided for bucket and vault exist and belong to the authenticated Basecamp account.
- Authentication Errors: Verify that the OAuth2 credentials are correctly set up and have sufficient permissions to create documents.
- HTML Content Issues: The content must be valid HTML according to Basecamp's rich text guidelines; invalid markup may cause API errors.
- Status Option Limitations: Only "Active" status is supported; attempting to use other statuses may result in errors.
Links and References
- Basecamp API Documentation (for detailed API behavior and document structure)
- Rich Text Guide for Basecamp Documents