Autentique

Overview

This 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 signature status of a particular document stored in Autentique.

Common scenarios include:

• Checking the current status and details of a contract or agreement before proceeding with further workflow steps.
• Retrieving signature information to verify who has signed or is pending signature.
• Auditing document creation date and properties for compliance or record-keeping.

Example: You have a document ID from a previous step or external system, and you want to get its name, creation date, whether it can be refused, if signatures must follow an order, and details about each signature (signer’s name, email, creation date, action, and signature link).

Properties

Output

The output JSON contains the following structure representing the document and its signatures:

{
  "document": {
    "id": "UUID",
    "name": "string",
    "refusable": true/false,
    "sortable": true/false,
    "created_at": "ISO8601 datetime string",
    "signatures": [
      {
        "public_id": "UUID",
        "name": "string",
        "email": "string",
        "created_at": "ISO8601 datetime string",
        "action": {
          "name": "string"  // e.g., SIGN, APPROVE
        },
        "link": {
          "short_link": "string"  // URL for signing
        }
      }
    ]
  }
}

• id: Document unique identifier.
• name: Document name/title.
• refusable: Indicates if the document can be refused by signatories.
• sortable: Indicates if signatures must be collected in a specific order.
• created_at: Timestamp when the document was created.
• signatures: Array of signature objects containing signer info and signature links.

No binary data is returned in this operation.

Dependencies

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

Troubleshooting

• Invalid Document ID: If the provided Document ID does not exist or is malformed, the API will likely return an error indicating the document was not found. Verify the ID format and existence.
• Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly configured.
• Network Issues: Connectivity problems to the Autentique API endpoint will result in request timeouts or errors.
• Permission Denied: If the authenticated user does not have access rights to the document, the API may return authorization errors.

To resolve these issues:

• Double-check the Document ID input.
• Confirm API credentials are valid and have required permissions.
• Test network connectivity.
• Review API response messages for specific error details.

Links and References

• Autentique API Documentation (official API docs, may require login)
• GraphQL Queries and Mutations (for understanding available operations)

This summary covers the static analysis of the "Get Document" operation within the Autentique node, focusing on its inputs, outputs, and usage context.