Autentique

Overview

The node integrates with the Autentique API to manage digital signature documents. Specifically, the Transfer Document operation allows transferring ownership of a document to another user or organization by specifying the recipient's email address. This is useful in workflows where document responsibility or control needs to be reassigned, such as handing off contracts, agreements, or signed documents to different departments or external collaborators.

Practical example:
You have a contract document that was initially created and managed by one team member, but now it needs to be transferred to another user for further processing or approval. Using this node operation, you can automate the transfer by providing the document ID and the receiver’s email, ensuring seamless handoff without manual intervention.

Properties

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: Public identifier of the signature.
  • name: Name of the signer.
  • email: Email of the signer.

This output confirms the successful transfer and provides the current state of the document and its signatures.

The node does not output binary data for this operation.

Dependencies

• Requires an API key credential for authenticating with the Autentique API.
• The node communicates with the Autentique API endpoint at https://api.autentique.com.br/v2.
• Proper permissions on the Autentique account are necessary to transfer documents.

Troubleshooting

• Common issues:

  • Invalid or missing Document ID: Ensure the document ID provided exists and is correctly formatted.
  • Invalid Receiver Email: Confirm the email address is valid and corresponds to a registered user or organization in Autentique.
  • Insufficient permissions: The API key used must have rights to transfer documents; otherwise, the request will fail.
  • Network or API errors: Check connectivity and API status if requests time out or return server errors.

• Error messages:

  • "Document not found": The specified document ID does not exist. Verify the ID.
  • "Unauthorized" or "Forbidden": The API key lacks permission to perform the transfer. Use credentials with appropriate access.
  • "Invalid email": The receiver email is not recognized. Confirm the email is correct and registered.

Resolving these typically involves verifying input parameters, checking API credentials, and ensuring the target user exists.

Links and References

• Autentique API Documentation (official API docs for detailed mutation and query usage)
• n8n Documentation (for general guidance on using custom nodes and credentials)