Actions19
Overview
This node operation allows you to move a document to a specific folder within the Autentique digital signature platform. It is useful for organizing documents by categorizing them into personal, organizational, or group folders. You can also remove a document from its current folder by leaving the destination folder ID empty.
Common scenarios:
- Automatically sorting signed contracts into client-specific folders.
- Moving draft documents out of a temporary folder once finalized.
- Organizing documents by department or project using organization or group folders.
Example:
You have a document with ID doc_12345 currently in folder folder_abcde. You want to move it to folder folder_xyz12 under the organization's context. This operation will update the document's folder assignment accordingly.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to be moved (required). |
| Destination Folder ID | The ID of the target folder where the document should be moved. Leave empty to remove folder association. |
| Current Folder ID | The ID of the folder where the document currently resides. Required if the document is already in a folder. |
| Context | The folder context type: - Personal (default) - Organization - Group |
Output
The output JSON contains the response from the API mutation that moves the document to the specified folder. Typically, this will be a confirmation of success or an updated state of the document's folder assignment.
No binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Autentique API.
- The node uses the Autentique GraphQL API endpoint at
https://api.autentique.com.br/v2. - Proper permissions are needed to modify document folder assignments within the Autentique account.
Troubleshooting
- Missing Document ID: The operation requires a valid document ID. Ensure this property is set and correctly references an existing document.
- Invalid Folder IDs: If the current or destination folder IDs are incorrect or do not exist, the API may return an error. Verify folder IDs before running the operation.
- Context Mismatch: Using an incorrect context value (e.g., specifying "Organization" context without proper folder ownership) might cause failures.
- Permission Denied: Insufficient permissions on the API key or user role can prevent moving documents between folders.
- Empty Destination Folder ID: Leaving this empty removes the document from any folder. Confirm this is intended to avoid accidental unfiling.
Links and References
- Autentique API Documentation (for detailed API usage and GraphQL schema)
- n8n Documentation - Creating Custom Nodes
- GraphQL Mutation Reference