Actions19
Overview
The node integrates with the Autentique API to manage digital document workflows, specifically focusing on digital signatures and biometric verification processes. The "Approve Biometric Verification" operation allows users to approve a pending biometric verification associated with a specific signature on a document. This is useful in scenarios where enhanced security is required for signing documents, ensuring that the signatory's identity is verified biometrically before final approval.
Practical examples include:
- Approving a biometric verification step in a contract signing workflow to comply with legal or organizational policies.
- Automating the approval of biometric verifications after manual review within an automated document management process.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document containing the signature to verify. |
| Signature ID | The public identifier of the signature related to the biometric verification. Obtained from document creation response or "Get Document" operation. |
| Verification ID | The numeric ID of the biometric verification to be approved. Obtained from the verifications field in the "Get Document" response. |
Output
The output JSON contains detailed information about the signature and its associated user after approving the biometric verification. It includes:
public_id: Public ID of the signature.name: Name of the signatory.email: Email address of the signatory.delivery_method: Method used to deliver the signature request.user: Object with user details includingid,name,email, andphone.verifications: Array of verification objects, each containing:id: Verification ID.type: Type of verification.verify_phone: Phone number used for verification if applicable.verified_at: Timestamp when verification was completed.max_attempt: Maximum allowed attempts.logs_attempt: Number of attempts logged.
This output confirms the biometric verification approval and provides updated status and metadata about the signature and user.
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/v2using GraphQL mutations. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Invalid or missing Document ID, Signature ID, or Verification ID will cause the mutation to fail.
- Network connectivity issues may prevent communication with the Autentique API.
- Insufficient permissions or invalid API credentials can result in authorization errors.
Error Messages:
- Errors indicating "verification not found" or "signature not found" suggest incorrect IDs; verify these values from the "Get Document" operation.
- Authentication errors imply misconfigured or expired API keys; ensure the API key credential is valid.
- Rate limiting or server errors from the API should be retried after some time or checked with Autentique support.
Links and References
- Autentique API Documentation (general reference for API usage)
- GraphQL Mutation for Approve Biometric Verification (if available publicly)
This summary focuses exclusively on the "Approve Biometric Verification" operation for the "Document" resource as requested.