Actions19
Overview
The node integrates with the Autentique API to manage digital document workflows, specifically focusing on documents requiring signatures. The "Sign" operation allows users to sign a specific document by its ID. This is useful in scenarios where a document has been prepared and sent for signature, and you want to programmatically trigger or confirm the signing action within an automation workflow.
Practical examples:
- Automatically signing a contract document after certain conditions are met.
- Triggering a signature confirmation step in a multi-step approval process.
- Integrating digital signature workflows into CRM or document management systems.
Properties
| Name | Meaning |
|---|---|
| Signature ID | The public identifier of the signature to be signed. This ID is obtained from the document creation response or via the "Get Document" operation under signatures.public_id. |
Output
The output of the "Sign" operation is the JSON response returned by the Autentique API after attempting to sign the document. Typically, this will include confirmation of the signing action or any relevant status updates related to the signature.
The node does not output binary data for this operation.
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
Common issues:
- Invalid or missing Signature ID: Ensure that the Signature ID provided corresponds to an existing signature on the document.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or API endpoint errors: Check connectivity to the Autentique API and ensure the base URL is accessible.
Error messages:
- Errors related to invalid UUIDs or missing parameters usually indicate incorrect input values; double-check the Signature ID and Document ID.
- Authorization errors suggest problems with the API key or credential setup.
- GraphQL errors may occur if the mutation syntax changes or if required fields are missing.
Resolving these typically involves verifying input parameters, ensuring credentials are valid, and checking API documentation for any updates.
Links and References
- Autentique API Documentation (general reference for API usage)
- GraphQL Mutation for Signing Documents (specific mutation used by the node)