Autentique

Overview

The node integrates with the Autentique API to manage digital document workflows, specifically enabling the addition of a new signatory to an existing document. This operation is useful in scenarios where you need to dynamically add participants who must sign a document after it has been created, such as adding a new stakeholder or approver in a contract signing process.

Practical examples include:

• Adding a new signatory to a contract that was initially sent to other parties.
• Including additional approvers in a document approval workflow without recreating the document.
• Dynamically managing signatories based on business logic or external triggers.

Properties

Example of the Signatory JSON:

{
  "name": "João Silva",
  "email": "joao@exemplo.com"
}

Output

The output JSON contains the updated document information after adding the signatory. It includes:

• id: The document's unique identifier.
• name: The document's name.
• signatures: An array of signature objects representing all signatories, each containing:
  • public_id: Unique identifier for the signature.
  • name: Name of the signatory.
  • email: Email address of the signatory.

This output allows subsequent nodes or workflows to access the current list of signatories and their details.

Dependencies

• Requires an API key credential for authenticating with the Autentique API.
• The node communicates with 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 requests.

Troubleshooting

• Invalid Document ID: If the provided Document ID does not exist or is malformed, the API may return an error indicating the document was not found. Verify the Document ID is correct.
• Malformed Signatory JSON: Ensure the signatory JSON is well-formed and includes required fields like name and email. Invalid JSON or missing fields can cause request failures.
• Authentication Errors: If the API key credential is missing or invalid, authentication errors will occur. Confirm the API key is correctly set up in n8n credentials.
• API Rate Limits or Downtime: Temporary issues with the Autentique API may cause errors. Retry after some time or check the service status.

Links and References

• Autentique API Documentation (general reference for API capabilities)
• GraphQL Mutation for Adding Signatory (if available publicly)

This summary covers the static analysis of the "Add Signatory" operation for the "Document" resource in the Autentique node.