Actions19
Overview
This node integrates with the Autentique API to manage digital document workflows, specifically enabling the creation of a direct signature link for a document's signatory. The "Create Signature Link" operation generates a short URL that can be shared with a signer, allowing them to access and sign the document directly.
Common scenarios include:
- Sending a quick-access signing link to a client or partner without requiring them to navigate through a portal.
- Automating signature requests in workflows where documents need to be signed by multiple parties.
- Integrating with communication tools to distribute signature links efficiently.
Example: After adding signatories to a contract document, you can use this operation to generate a direct signing link for a specific signatory, which can then be sent via email or messaging platforms.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document for which the signature link is to be created. |
| Signature ID | The public identifier of the specific signature (signatory) within the document. This ID is obtained from document creation or retrieval responses. |
Output
The output JSON contains a single field:
short_link: A string representing the shortened URL that directs the signatory to the document's signing page.
Example output JSON:
{
"short_link": "https://autentique.com.br/s/abc123"
}
This link can be used directly to allow the signatory to sign the document.
Dependencies
- Requires an API key credential for authenticating with the Autentique API.
- The node makes a POST request to the Autentique GraphQL endpoint (
https://api.autentique.com.br/v2/graphql). - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Invalid Document ID or Signature ID: If either ID is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify IDs by retrieving the document or signature details first.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Connectivity problems may cause request failures; check network access to the Autentique API endpoint.
- Expired or Revoked Signatures: If the signature is no longer valid or the document status prevents signing, the link creation might fail.
Links and References
- Autentique API Documentation (general reference for API capabilities)
- GraphQL Mutation for Creating Signature Link (if available publicly)
This summary focuses on the "Create Signature Link" operation under the "Document" resource as requested.