Actions22
- Document Actions
- Email Template Actions
- Folder Actions
- Organization Actions
- User Actions
Document → Sign
AI-generatedOverview
This node operation allows users to sign a specific document using the Autentique API. It is useful in workflows where digital document signing is required, such as contract approvals, legal document processing, or any scenario needing verified electronic signatures. The operation sends a GraphQL mutation to the Autentique API to sign the document identified by its unique document ID.
Use Case Examples
- Automatically sign a contract document after all required fields are filled.
- Trigger a document signing process as part of an approval workflow in a business process automation.
Properties
| Name | Meaning |
|---|---|
| Signature ID | The public ID of the signature to be used for signing the document. This ID is obtained from the document creation response or from the 'Get Document' operation under signatures.public_id. |
Output
JSON
signDocument- Indicates the result of the sign document mutation, typically a confirmation or status of the signing operation.
Dependencies
- Requires an API key credential for the Autentique API to authenticate requests.
Troubleshooting
- Ensure the 'Signature ID' is correctly provided and corresponds to a valid signature on the document.
- Verify that the document ID is valid and the document is in a state that allows signing.
- Check API authentication credentials if requests fail due to authorization errors.
- Network issues or incorrect API endpoint configuration can cause request failures; verify connectivity and base URL settings.
Links
- Autentique API Documentation - Official API documentation for Autentique, providing details on available operations including document signing.