Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Overview

The "Resend Signatures" operation in the Autentique node allows users to resend pending signature notifications for a specific document. This is useful when signatories have not yet completed their signatures and need a reminder or if the original notification was missed or lost. For example, if a contract sent for digital signing has some recipients who haven't signed yet, this operation can trigger the system to send them another notification email prompting them to sign.

Properties

Name Meaning
Document ID The unique identifier of the document for which pending signature notifications will be resent. Example format: doc_xxxxx

Output

The output JSON contains the updated document information after resending the signature notifications. It includes:

  • id: The document's unique identifier.
  • name: The name of the document.
  • signatures: An array of signature objects, each containing:
    • public_id: The public identifier of the signature request.
    • name: The name of the signatory.
    • email: The email address of the signatory.

This output confirms that the resend action was performed and provides the current state of the document's signatures.

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 within n8n is necessary for successful operation.

Troubleshooting

  • Common Issues:

    • Invalid or missing Document ID: Ensure the Document ID is correctly provided and corresponds to an existing document.
    • Authentication errors: Verify that the API key credential is valid and properly configured.
    • Network issues: Confirm that the n8n instance can reach the Autentique API endpoint.
  • Error Messages:

    • "Unauthorized" or "Authentication failed": Check API key credentials.
    • "Document not found": Verify the Document ID is correct.
    • GraphQL errors: Review the query variables and ensure all required parameters are set.

Links and References

Discussion