Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions18

Overview

The node integrates with the Autentique API to manage digital signature documents. Specifically, the Document - Get operation retrieves detailed information about a specific document by its ID. This is useful when you want to fetch metadata and status of a document that is managed within Autentique’s digital signature platform.

Common scenarios include:

  • Checking the status and details of a contract or agreement before proceeding with further workflow steps.
  • Retrieving signatory information and timestamps for audit or compliance purposes.
  • Integrating document data into other systems or dashboards for monitoring signature progress.

Example: You have sent a contract for signature and want to verify if it has been signed or is still pending. Using this node operation, you provide the document ID and get back all relevant details including signatories and creation date.

Properties

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

Output

The output JSON contains detailed information about the requested document, including:

  • id: The document's unique identifier.
  • name: The name/title of the document.
  • refusable: Boolean indicating if the document can be refused.
  • sortable: Boolean indicating if signatures must follow a specific order.
  • created_at: Timestamp of when the document was created.
  • signatures: An array of signature objects, each containing:
    • public_id: Public identifier of the signature.
    • name: Name of the signatory.
    • email: Email address of the signatory.
    • created_at: Timestamp when the signature was created.
    • action: Object with the action name related to the signature (e.g., "signed").
    • link: Object containing a short link URL for signing.

This structured output allows workflows to programmatically access document and signature details.

Dependencies

  • Requires an API key credential for authenticating with the Autentique API.
  • The node makes HTTP POST requests to the Autentique GraphQL endpoint at https://api.autentique.com.br/v2/graphql.
  • Proper configuration of the API key credential in n8n is necessary for successful requests.

Troubleshooting

  • Invalid Document ID: If the provided document ID does not exist or is malformed, the API will return an error. Verify the ID format and existence in your Autentique account.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Ensure the API key credential is correctly set up in n8n.
  • Network Issues: Connectivity problems may prevent reaching the Autentique API. Check network settings and firewall rules.
  • Permission Denied: The API user associated with the API key must have permission to access the specified document.

Links and References

Discussion