Actions18
Overview
The "Remove Signatory" operation in the Autentique node allows users to remove a signatory from a specific document. This is useful when a signer should no longer be part of the signing process, for example, if they were added by mistake or their participation is no longer required.
Typical scenarios include:
- Correcting errors in the list of signatories before finalizing a document.
- Managing dynamic signing workflows where participants may change.
- Revoking access for a particular signer without deleting the entire document.
Example use case: You have sent a contract for signature but realize one recipient should not sign it. Using this operation, you can remove that signatory from the document, preventing them from signing.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document from which the signatory will be removed. |
| Signature ID | The unique identifier of the signature (signatory) to be removed from the document. |
Output
The output JSON contains the updated document information after the removal of the signatory. It includes:
id: The document's unique identifier.name: The name of the document.signatures: An array of remaining signatures/signatories on the document, each with:public_id: The public identifier of the signature.name: The name of the signatory.email: The email address of the signatory.
This output confirms the successful removal and shows the current state of signatories.
Dependencies
- Requires an API key credential for authenticating requests to the Autentique API.
- The node communicates with the Autentique GraphQL API endpoint at
https://api.autentique.com.br/v2. - Proper configuration of the API key credential in n8n is necessary for authorization.
Troubleshooting
- Missing or invalid Document ID or Signature ID: The operation requires both IDs to identify the document and the signatory to remove. Ensure these are correctly provided.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Signatory not found: If the specified signature ID does not exist on the document, the API may return an error. Double-check the signature ID.
- Network or API downtime: Temporary issues with the Autentique service could cause failures; retry later or check service status.
Links and References
- Autentique API Documentation (general reference for API capabilities)
- GraphQL Mutation for Removing Signatory (if available publicly)
This summary is based solely on static analysis of the provided source code and property definitions.