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 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 tasks, messages, or records in an external system.
For example, you might use this node to upload a PDF report generated during a workflow run or attach images captured from another service.
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 other relevant details returned by the API.
If the node supports binary data (file content), it would handle the file upload accordingly, but based on the provided code and properties, the focus is on specifying the file name for the upload rather than handling raw binary data directly.
Dependencies
- Requires an API key credential for authentication with the external service.
- The node uses a base URL constructed dynamically using credentials.
- The underlying API interaction is based on OpenAPI specifications bundled with the node.
Troubleshooting
- Missing or invalid file name: Since the "Name" property is required, ensure it is provided and correctly formatted.
- Authentication errors: Verify that the API key or OAuth2 token is valid and has sufficient permissions.
- API endpoint issues: Check that the base URL and resource paths are correct and accessible.
- File upload failures: Confirm that the file content is properly attached if applicable, and that the API accepts the file format.
Links and References
- Refer to the external service's API documentation for details on attachment creation endpoints.
- Consult n8n documentation on how to configure API credentials and manage file uploads within workflows.