Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions18

Overview

This node integrates with the Autentique API to manage digital document workflows, specifically focusing on documents that require signatures. The "Sign" operation allows users to digitally sign a specific document by referencing its unique Document ID and the Signature ID of the signature request.

Common scenarios for this node include automating the signing process in contract management systems, legal document workflows, or any business process requiring verified digital signatures. For example, after sending a contract for signature, this node can be used to programmatically confirm a signature once the signer has completed their part.

Properties

Name Meaning
Document ID The unique identifier of the document to be signed (e.g., doc_xxxxx).
Signature ID The unique identifier of the specific signature request within the document (e.g., sig_xxxxx).

Output

The output JSON contains the updated document information after the signing action is performed. It includes:

  • id: The document's unique identifier.
  • name: The name of the document.
  • signatures: An array of signature objects related to the document, each containing:
    • public_id: Public identifier of the signature.
    • name: Name of the signer.
    • email: Email of the signer.
    • action: An object with the name of the action performed (e.g., "signed").

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Autentique API.
  • The node communicates with the Autentique API endpoint at https://api.autentique.com.br/v2.
  • Proper configuration of the API key credential in n8n is necessary for successful operation.

Troubleshooting

  • Invalid Document ID or Signature ID: If either ID is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up and valid.
  • Permission Issues: The authenticated user must have permission to sign the specified document. Lack of permissions may result in authorization errors.
  • Network or API Downtime: Temporary network issues or Autentique API downtime can cause request failures. Retry after some time or check the API status.

Links and References

Discussion