Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Overview

This node integrates with the Autentique API to manage digital documents for electronic signatures. Specifically, the Delete Document operation allows users to delete a document by its unique identifier. This is useful in workflows where documents need to be programmatically removed after completion, cancellation, or error handling.

Typical use cases include:

  • Automatically cleaning up draft or obsolete documents.
  • Removing documents that were created in error.
  • Managing document lifecycle by deleting signed or rejected documents no longer needed.

Example: After a contract is signed and archived elsewhere, this node can delete the original document from Autentique to keep the workspace tidy.

Properties

Name Meaning
Document ID The unique identifier of the document to delete. Example format: doc_xxxxx.

Output

The output JSON contains the deleted document's basic information:

{
  "id": "string",
  "name": "string"
}
  • id: The ID of the deleted document.
  • name: The name/title of the deleted document.

No binary data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Autentique API.
  • The node sends a GraphQL mutation request to the endpoint https://api.autentique.com.br/v2/graphql.
  • Proper network access to the Autentique API is necessary.

Troubleshooting

  • Missing or invalid Document ID: Ensure the Document ID property is provided and correctly formatted. An empty or incorrect ID will cause the API to reject the request.
  • Authentication errors: Verify that the API key credential is valid and has permissions to delete documents.
  • Document not found: If the document ID does not exist or was already deleted, the API may return an error indicating the document cannot be found.
  • API rate limits or downtime: Temporary failures might occur due to API limits or service outages; retrying later may help.

Links and References


This summary is based on static analysis of the node's source code and input properties related to the Document Delete operation.

Discussion