Actions80
- Todos Actions
- 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
Overview
This node operation allows you to create an attachment by uploading a file with a specified name. It is useful in scenarios where you need to programmatically add files or documents as attachments within a workflow, such as adding supporting documents to project management tools, customer records, or any system that supports attachments.
For example, you might use this node to upload a PDF report generated during a workflow or attach images captured from an external source to a task or record.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the file being uploaded as an attachment. This is a required string property and typically represents the filename including extension (e.g., "report.pdf"). |
Output
The output contains a JSON object representing the created attachment. This typically includes metadata about the uploaded file such as its ID, URL, name, size, and possibly timestamps or other relevant information returned by the API after successful creation.
If the node supports binary data output, it would represent the actual file content or a reference to it, but based on the provided code and properties, the focus is on the metadata of the created attachment.
Dependencies
- Requires an API key credential for authentication with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the Basecamp account ID from credentials.
- The request headers specify JSON content type and accept JSON responses.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
- Missing or invalid file name: Since the "Name" property is required, omitting it or providing an empty string will likely cause the API call to fail. Ensure the file name is correctly set.
- Authentication errors: If the API key or OAuth token is missing, expired, or incorrect, the node will fail to authenticate. Verify the credentials configuration.
- API endpoint issues: The base URL depends on the Basecamp account ID; if this is incorrect or missing, requests will fail.
- File upload failures: Network issues or API limits may cause upload failures. Check error messages for HTTP status codes and retry if necessary.
Links and References
- Basecamp API Documentation
- n8n documentation on Creating Attachments (general guidance)