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 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 the workflow or attach images captured from an external source.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the file being uploaded as an attachment. This is a required string property and represents the filename that will be associated with the uploaded file. |
Output
The node outputs JSON data representing the result of the attachment creation operation. This typically includes metadata about the newly created attachment, such as its ID, URL, or status confirmation. If the node supports binary data output (e.g., the actual file content), it would be included in a binary field, but based on the provided code and properties, the focus is on creating/uploading the attachment rather than returning binary data.
Dependencies
- Requires an API key credential for authentication with the target service.
- The node uses a base URL constructed dynamically using credentials (e.g., a Basecamp ID).
- The node depends on an OpenAPI specification for request building and validation.
Troubleshooting
- Missing or invalid file name: Since the "Name" property is required, omitting it or providing an empty string will likely cause errors. Ensure the file name is correctly set.
- Authentication errors: If the API key or authentication token is missing or invalid, the node will fail to connect to the service.
- Network or API errors: Issues like network timeouts or API rate limits can cause failures. Check connectivity and API usage limits.
- Incorrect base URL or credentials: The base URL depends on credentials; incorrect values will lead to failed requests.
Links and References
- Refer to the official API documentation of the target service for details on attachment creation endpoints.
- Consult n8n documentation on how to configure API credentials and use nodes with file uploads.