Actions18
Overview
This node integrates with the Autentique API to manage digital document workflows, specifically focusing on documents requiring signatures and biometric verification. The "Reject Biometric Verification" operation allows users to reject a pending biometric verification request for 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 is illegible or does not match the expected identity.
Practical examples:
- A company automating contract signing can use this node to programmatically reject biometric verifications that do not meet compliance standards.
- Legal teams can automate the rejection of biometric verifications if the submitted biometric data is suspicious or incomplete.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document for which the biometric verification is being rejected. |
| Signature ID | The unique identifier of the signature request associated with the biometric verification. |
| Rejection Reason | Optional text describing why the biometric verification was rejected (e.g., "Documento ilegível"). |
Output
The output JSON contains details about the biometric verification rejection result, including:
id: The document's unique identifier.status: The current status of the document after rejection.rejected_at: Timestamp indicating when the biometric verification was rejected.rejection_reason: The reason provided for rejecting the biometric verification.
This output confirms the rejection action and provides metadata useful for logging or further processing.
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 key credential within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or missing Document ID or Signature ID will cause the API call to fail.
- Network connectivity issues may prevent communication with the Autentique API.
- Insufficient permissions or invalid API credentials will result in authentication errors.
Error Messages:
- Authentication errors typically indicate problems with the API key; verify the credential setup.
- Validation errors may occur if required parameters are missing or malformed; ensure all required fields are correctly filled.
- API rate limits might be enforced by Autentique; if hitting limits, consider retry strategies or contact support.
Links and References
- Autentique API Documentation (general reference for API capabilities)
- GraphQL Mutation for Rejecting Biometric Verification (if available publicly)
This summary focuses exclusively on the "Reject Biometric Verification" operation under the "Document" resource, based on the provided source code and property definitions.