Actions18
- Contact Actions
- Message Actions
- Conversation Actions
- Note Actions
- File Actions
Overview
This node integrates with the Superchat API to manage files among other resources. Specifically, the "Delete A File" operation allows users to delete a file from Superchat by specifying its unique ID. This is useful in scenarios where you want to programmatically remove outdated or unwanted files stored in Superchat, such as cleaning up attachments or media no longer needed.
Practical example: Automatically deleting files after processing them in a workflow to save storage space or maintain data hygiene.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the file to delete. This is required to specify which file should be removed from Superchat. |
Output
The node outputs a JSON array containing the results of the delete operation for each input item. Each element in the output corresponds to one deletion attempt and typically includes confirmation details or status returned by the Superchat API about the deleted file.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Superchat API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node depends on the internal Superchat API client methods bundled within the node's codebase.
Troubleshooting
- Common issues:
- Providing an invalid or non-existent file ID will likely result in an error from the API indicating the file could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Error messages:
- "File not found" or similar indicates the specified ID does not correspond to any existing file.
- Authentication errors suggest checking the API key or token configuration.
- Resolution:
- Verify the file ID is correct and exists in Superchat.
- Ensure the API credentials are properly set up and have sufficient permissions to delete files.
Links and References
- Superchat API Documentation (official resource for API endpoints and usage)