Actions19
Overview
The "Transfer Document" operation in this node allows transferring a digital document managed by the Autentique API from one user or organization to another user via their email address. This is useful when ownership or responsibility for a document needs to be reassigned, such as handing over contract management to a different team member or transferring signed documents to a client or partner.
Practical examples:
- Transferring a contract document to a new account manager's email.
- Moving a signed agreement to another department's user for further processing.
- Reassigning document ownership after employee turnover.
This operation ensures that the specified document and its associated signatures are transferred securely to the intended recipient.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to transfer. Example format: doc_xxxxx |
| Receiver Email | The email address of the user who will receive the document. Example: user@example.com |
Output
The output JSON contains the updated document information after the transfer, including:
id: The document's unique identifier.name: The name/title of the document.signatures: An array of signature objects associated with the document, each containing:public_id: Unique identifier of the signature.name: Name of the signer.email: Email of the signer.
This output confirms the successful transfer and provides details about the document and its signatories.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Autentique API.
- The node makes a POST request to the Autentique GraphQL endpoint at
https://api.autentique.com.br/v2. - Proper permissions on the API key are necessary to perform document transfers.
Troubleshooting
Common issues:
- Invalid or missing Document ID: Ensure the document ID provided exists and is correctly formatted.
- Incorrect receiver email: Verify the email address is valid and corresponds to a registered user in the system.
- Insufficient permissions: The API key used must have rights to transfer documents.
- Network or API errors: Check connectivity and API status.
Error messages:
- "Document not found": The provided Document ID does not exist; verify the ID.
- "Unauthorized" or "Forbidden": The API key lacks permission; check credentials and scopes.
- "Invalid email address": The receiver email is malformed or unregistered; correct the email.
Resolving these typically involves verifying input parameters, ensuring valid credentials, and confirming API availability.
Links and References
- Autentique API Documentation (official API docs for detailed mutation and query info)
- GraphQL Basics (to understand the GraphQL queries/mutations used)