Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions18

Overview

The "Get Many" operation of the Document resource in this node retrieves multiple documents from the Autentique digital signature platform. It allows users to fetch a paginated list of documents with details such as document ID, name, creation date, and associated signatures. This operation is useful for scenarios where you need to display or process batches of documents, such as generating reports, syncing document lists, or managing document workflows in bulk.

Practical examples:

  • Fetching the first 50 documents created in an organization to display in a dashboard.
  • Paginating through documents to find those pending signatures.
  • Integrating document metadata into other systems for audit or compliance purposes.

Properties

Name Meaning
Limit Max number of results to return. Specifies how many documents to retrieve per request.
Page Page number of the results to return. Used for pagination to navigate through document pages.

Output

The output JSON contains a paginated structure with the following fields:

  • data: An array of document objects, each including:

    • id: The unique identifier of the document.
    • 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 when the document was created.
    • signatures: Array of signature objects related to the document, each containing:
      • public_id: Public identifier of the signature.
      • name: Name of the signer.
      • email: Email address of the signer.
      • created_at: Timestamp when the signature was created.
      • action: Object with the action name related to the signature (e.g., signed).

  • Pagination metadata:

    • total: Total number of documents available.
    • per_page: Number of documents per page.
    • current_page: Current page number.
    • last_page: Last available page number.

This structured output enables easy handling of document lists and their associated signatures within workflows.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Requesting a page number beyond the last page may return empty data arrays.
    • Setting the limit too high might lead to performance issues or API rate limiting.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • GraphQL errors may occur if parameters are malformed; ensure limit and page are positive integers.
    • Network errors suggest connectivity problems; check internet access and API availability.

Links and References

Discussion