Autentique Trigger icon

Autentique Trigger

Recebe notificações de eventos da Autentique via webhook

Overview

The Autentique Trigger node listens for webhook notifications from the Autentique platform, which provides digital document signing services. It triggers workflows in n8n when specific events related to documents or signatories occur, such as when a document is created, signed, rejected, or when a particular signatory signs or rejects.

This node is useful for automating processes that depend on document lifecycle events, for example:

  • Automatically updating a CRM or database when a contract is fully signed.
  • Sending notifications or follow-ups when a document is rejected.
  • Tracking signature progress by monitoring individual signatories' actions.

Properties

Name Meaning
Evento Type of event to receive notifications for. Options:
- Documento Assinado (document_signed)
- Documento Criado (document_created)
- Documento Rejeitado (document_rejected)
- Signatário Assinou (signatory_signed)
- Signatário Rejeitou (signatory_rejected)
- Todos Os Eventos (*) (all events)
Apenas Documentos Específicos Whether to filter notifications only for specific documents (true/false).
IDs Dos Documentos Comma-separated list of document IDs to filter by. Only used if "Apenas Documentos Específicos" is true. Leave blank to accept all documents.
Validar Assinatura Whether to validate the webhook signature using the API token (true/false). Ensures the webhook call is authentic.

Output

The node outputs JSON data containing the webhook payload with the following structure:

{
  "event": "string",          // The event type received (e.g., "document_signed")
  "timestamp": "string",      // Timestamp of the event, ISO string format
  "document": {               // Object with details about the document involved
    // document properties as provided by Autentique
  },
  "signatory": {              // Object with details about the signatory involved (if applicable)
    // signatory properties
  },
  "organization": {           // Object with details about the organization (if provided)
    // organization properties
  },
  "webhook_data": {           // Raw webhook payload as received
    // full webhook data
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token credential for the Autentique API.
  • The node uses the Autentique GraphQL API to optionally load document options.
  • The webhook expects HTTP POST requests from Autentique with specific headers for signature validation (x-autentique-signature and x-autentique-timestamp).
  • Proper configuration of the webhook URL in Autentique's system is necessary to receive events.

Troubleshooting

  • Missing or invalid webhook signature:
    If the webhook request does not contain the required signature headers or the signature validation fails, the node will throw an error indicating an invalid webhook signature.
    Resolution: Ensure the webhook sender (Autentique) includes the correct signature headers and that the API token configured in n8n matches the one used by Autentique.

  • Event type mismatch:
    If the incoming webhook event does not match the selected event type (unless "Todos Os Eventos" is selected), the node ignores the event and returns a 200 status with an "Event type mismatch" message.
    Resolution: Verify that the node's event property matches the expected event types you want to process.

  • Document filtering issues:
    When filtering by specific document IDs, if the incoming event's document ID is not in the list, the event is ignored with a corresponding message.
    Resolution: Check that the document IDs are correctly entered, comma-separated, and correspond to valid documents.

  • API errors when loading documents:
    Errors during fetching documents for dropdown options may occur due to network issues or invalid credentials.
    Resolution: Confirm API token validity and network connectivity.

Links and References

Discussion