Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions19

Overview

The "Add Signatory" operation in the Document resource allows you to add a new signatory to an existing document for digital signing or approval. This node interacts with the Autentique API to create a signer entry associated with a specific document, specifying how the signatory will be contacted and what action they are expected to perform.

This operation is useful in workflows where documents require multiple signatures or approvals from different parties. For example, you can automate adding a client as a signatory by email or phone, specifying whether they should sign, approve, witness, or recognize the signature.

Practical examples:

  • Adding a customer to sign a contract via email.
  • Adding a witness to a legal document using their phone number with WhatsApp delivery.
  • Generating a signing link for a signatory identified only by name.

Properties

Name Meaning
Document ID The unique identifier of the document to which the signatory will be added.
Contact Method Method to contact the signatory: Email, Phone, or Name Only (generates a signing link).
Signatory Email Email address of the signatory (required if Contact Method is Email).
Signatory Phone Phone number of the signatory in international format (required if Contact Method is Phone).
Signatory Name Name of the signatory (optional for Email/Phone, mandatory if Contact Method is Name Only).
Action The action the signatory must perform on the document: Sign, Approve, Sign as Witness, Recognize.
Delivery Method Method to deliver the signing invitation when Contact Method is Phone: WhatsApp or SMS.

Output

The output JSON contains details about the newly created signatory, including:

  • public_id: Unique identifier of the signatory.
  • name: Name of the signatory.
  • email: Email of the signatory (if applicable).
  • delivery_method: How the invitation was delivered.
  • action: The action assigned to the signatory.
  • link: Contains the signing link information (id and short_link).
  • created_at: Timestamp when the signatory was added.

This output can be used downstream in your workflow to track signatories, send reminders, or generate reports.

Dependencies

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

Troubleshooting

  • Missing Required Fields: Ensure that the Document ID and required signatory fields (email, phone, or name depending on contact method) are provided.
  • Invalid Contact Method Combinations: If Contact Method is Phone, Delivery Method must be specified; if Email, ensure a valid email is given.
  • API Authentication Errors: Verify that the API key credential is correctly set up and has permissions to modify documents.
  • GraphQL Errors: Check the error messages returned by the API for issues like invalid document IDs or signatory data.
  • Phone Number Format: Phone numbers must be in international format (e.g., +5511999999999); incorrect formatting may cause failures.

Links and References

Discussion