Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions19

Overview

This node integrates with the Autentique API to manage digital document workflows, specifically focusing on biometric verification rejection for documents. The "Reject Biometric Verification" operation allows users to reject a pending biometric verification associated with a specific signature on a document. This is useful in scenarios where the biometric verification fails or is deemed invalid, such as when the biometric data does not match or the document is illegible.

Practical examples include:

  • A legal department rejecting a biometric verification attempt on a contract due to poor fingerprint scan quality.
  • An HR team rejecting an employee's biometric approval on a sensitive document if the verification was performed incorrectly.

Properties

Name Meaning
Document ID The unique identifier of the document containing the biometric verification to reject.
Signature ID The public identifier of the signature related to the biometric verification. Obtained from document creation or retrieval.
Verification ID The numeric ID of the biometric verification to be rejected. Retrieved from the document's verifications list.
Rejection Reason Optional text describing the reason for rejecting the biometric verification (e.g., "Documento ilegível").

Output

The output JSON contains detailed information about the signature after the biometric verification rejection, including:

  • public_id: The public ID of the signature.
  • name: Name of the signatory.
  • email: Email of the signatory.
  • delivery_method: How the signature invitation was delivered.
  • user: Object with user details (id, name, email, phone).
  • verifications: Array of verification objects showing current status and logs, each with fields like id, type, verify_phone, verified_at, max_attempt, and logs_attempt.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Autentique API.
  • The node sends GraphQL POST requests to https://api.autentique.com.br/v2.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing Document ID, Signature ID, or Verification ID will cause errors.
    • Network connectivity issues may prevent successful API calls.
    • Insufficient permissions or invalid API credentials can lead to authorization failures.

  • Error Messages:

    • Errors indicating "verification_id not found" suggest the provided Verification ID does not exist or is incorrect.
    • Authentication errors imply problems with the API key credential setup.
    • GraphQL errors may occur if required parameters are missing or malformed.

  • Resolutions:

    • Verify all IDs are correct and correspond to existing entities in Autentique.
    • Ensure the API key credential is valid and has appropriate permissions.
    • Check network connectivity and endpoint accessibility.

Links and References

Discussion