Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions18

Overview

This node integrates with the Autentique API to create a new digital document for signature workflows. It allows users to upload a document file (in Base64 format), specify signatories, and configure various signing options such as signature order, reminders, deadlines, and signature styles.

Common scenarios include automating contract signing processes, sending service agreements for electronic signatures, or managing legally binding documents digitally. For example, a company can use this node to send a service contract PDF to multiple clients for signature, set up automatic email reminders, and enforce that signatories must scroll through the entire document before signing.

Properties

Name Meaning
Document Name The name/title of the document being created (e.g., "Service Agreement").
File Content (Base64) The content of the document file encoded in Base64 format.
Signatures JSON array of signatories, each with name and email, who will be requested to sign the document.
Refusable Whether the document can be refused by signatories (boolean).
Sortable Whether signatures must follow a specific order (boolean).
Message Custom message sent via email to all signatories.
Reminder Frequency of automatic email reminders: None, Daily, or Weekly.
Footer Position Position of the footer on the document: None, Bottom, Left, or Right.
Qualified Signature Enable qualified digital signature using certificates (boolean).
Scrolling Required Require signatories to scroll through the entire document before signing (boolean).
Stop on Rejected Stop other signatories from signing if the document is refused by someone (boolean).
New Signature Style Enable new style for signature fields (boolean).
Show Audit Page Show an audit page at the end of the document summarizing actions (boolean, default true).
Ignore CPF Remove requirement for signatories to fill in CPF (Brazilian tax ID) (boolean).
Ignore Birthdate Remove requirement for signatories to fill in birthdate (boolean).
Deadline ISO date/time string specifying the deadline for signatures.
Organization ID Optional ID of the organization under which to create the document.
Folder ID Optional ID of the folder where the document should be created.

Output

The node outputs JSON data representing the newly created document, including:

  • id: Unique identifier of the document.
  • name: Document name.
  • refusable: Boolean indicating if the document can be refused.
  • sortable: Boolean indicating if signature order is enforced.
  • created_at: Timestamp of creation.
  • signatures: Array of signature objects, each containing:
    • public_id: Public identifier of the signature.
    • name: Name of the signatory.
    • email: Email of the signatory.
    • created_at: Timestamp when the signature request was created.
    • action: Object describing the action (e.g., signing).
    • link: Object containing a short link for signing.
    • user: User information related to the signature.

No binary output is produced by this operation.

Dependencies

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

Troubleshooting

  • Invalid Base64 File Content: If the file content is not properly Base64 encoded, the API may reject the document creation. Ensure the file content is correctly encoded.
  • Missing Required Fields: The fileContent and signatures properties are required. Omitting them will cause errors.
  • Invalid Signatories JSON: The signatures property must be a valid JSON array with objects containing at least name and email. Malformed JSON or missing fields will cause failures.
  • API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Deadline Format: The deadlineAt property must be a valid ISO datetime string; otherwise, the API may reject it.
  • Organization or Folder IDs: If provided, these must correspond to existing entities in the Autentique system; invalid IDs will cause errors.

Links and References

Discussion