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
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 knowledge base articles from other data sources.
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 being 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 related metadata. There is no binary output.
Dependencies
- Requires an API authentication token credential for Basecamp.
- The node uses the Basecamp API endpoint constructed dynamically based on the authenticated user's Basecamp account ID.
- No additional environment variables are needed beyond the API credentials.
Troubleshooting
- Missing or invalid Bucket Id or Vault Id: Ensure these numeric IDs correspond to existing buckets and vaults in your Basecamp account.
- Invalid HTML content: The content must be valid HTML according to Basecamp's rich text guidelines; malformed HTML may cause errors.
- Authentication errors: Verify that the API key or OAuth token is correctly configured and has sufficient permissions to create documents.
- Status option limitations: Only "Active" status is supported; using other values may result in errors.