Actions18
Overview
The node integrates with the Autentique API to manage digital document workflows, specifically focusing on creating a direct signature link for a document's signatory. This operation generates a URL that can be shared with a signer, allowing them to access and sign the document directly without additional navigation.
This is useful in scenarios where you want to streamline the signing process by providing signatories with a quick-access link, such as sending it via email or messaging platforms. For example, after adding signatories to a contract, you can create and send them a signature link to expedite the signing process.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to which the signature link will be created. |
| Signature ID | The unique identifier of the specific signature (signatory) within the document. |
Output
The output JSON contains two main fields:
link: A string representing the direct URL to the signature page for the specified signatory.expires_at: A timestamp indicating when the signature link will expire.
Example output structure:
{
"link": "https://autentique.com.br/signature/abc123",
"expires_at": "2024-07-01T12:00:00Z"
}
This allows downstream nodes or users to retrieve and use the signature link before it expires.
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 in n8n is necessary for successful operation.
Troubleshooting
- Invalid Document ID or Signature ID: If either ID is incorrect or does not exist, the API may return an error indicating the resource was not found. Verify the IDs are correct and correspond to existing documents and signatures.
- Expired or Revoked API Key: Authentication failures may occur if the API key is invalid or expired. Ensure the API key credential is valid and has appropriate permissions.
- Network Issues: Connectivity problems can cause request failures. Check network connectivity and API availability.
- Permission Denied: If the authenticated user does not have permission to create signature links for the document, the API will reject the request. Confirm user permissions in Autentique.
Links and References
- Autentique API Documentation (general reference for API usage)
- Autentique GraphQL API (endpoint used by this node)
This summary focuses exclusively on the "Create Signature Link" operation under the "Document" resource as requested.