Actions18
Overview
This node integrates with the Autentique API to manage digital document workflows, specifically focusing on document signing and verification processes. The "Approve Biometric Verification" operation allows users to approve a pending biometric verification request for a specific signature on a document. This is useful in scenarios where a signatory's identity needs to be confirmed biometrically before finalizing their signature.
Practical examples include:
- Approving a biometric verification after a user has submitted their biometric data for identity confirmation.
- Automating the approval step in a workflow that requires biometric validation of signatories.
- Ensuring compliance by programmatically confirming biometric verifications within document signing processes.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document for which the biometric verification is approved. |
| Signature ID | The unique identifier of the signature associated with the biometric verification request. |
Output
The output JSON contains the updated status of the biometric verification for the specified signature on the document. It includes:
id: The document ID.status: The current status of the biometric verification after approval.verified_at: Timestamp indicating when the biometric verification was approved.
This output confirms that the biometric verification has been successfully approved and provides relevant metadata about the verification state.
Dependencies
- Requires an API key credential for authenticating requests to the Autentique API.
- The node sends GraphQL POST requests to the endpoint
https://api.autentique.com.br/v2/graphql. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Document ID or Signature ID parameters will cause the operation to fail.
- Authentication errors if the API key credential is not configured correctly.
- Network issues or API downtime may prevent successful communication with the Autentique service.
Error Messages:
- Errors related to invalid IDs typically indicate that the provided Document ID or Signature ID does not exist or is malformed.
- Authentication errors suggest checking the API key credential setup.
- GraphQL errors returned from the API should be reviewed for detailed messages; ensure all required parameters are provided.
Resolution Tips:
- Verify that the Document ID and Signature ID are correct and correspond to existing entities in Autentique.
- Confirm that the API key credential is valid and has sufficient permissions.
- Check network connectivity and retry if transient errors occur.
Links and References
- Autentique API Documentation (general reference for API capabilities)
- GraphQL Mutation for Approving Biometric Verification (if available publicly)
This summary focuses exclusively on the "Approve Biometric Verification" operation under the "Document" resource as requested.