Autentique Trigger icon

Autentique Trigger

Recebe notificações de eventos da Autentique via webhook

Autentique Trigger

AI-generated

Overview

This node acts as a webhook trigger for Autentique events, receiving notifications about document-related activities such as document creation, signing, rejection, and signatory actions. It is useful for automating workflows that depend on real-time updates from Autentique, such as processing signed documents, tracking document status changes, or handling signatory responses.

Use Case Examples

  1. Trigger a workflow when a document is fully signed to start a post-signature process.
  2. Receive notifications for specific documents to update a database or notify users.
  3. Filter events to only process document creation events for audit logging.

Properties

Name Meaning
Evento Type of event to receive notifications for, such as document signed, created, rejected, signatory signed, signatory rejected, or all events.
Apenas Documentos Específicos Whether to filter notifications to only specific documents.
IDs Dos Documentos Comma-separated list of document IDs to filter notifications. Only used if filtering to specific documents is enabled.
Validar Assinatura Whether to validate the webhook signature using the API token to ensure authenticity of the webhook call.

Output

JSON

  • event - The event type received from the webhook.
  • timestamp - Timestamp of the event, either from the webhook or the current time if not provided.
  • document - Details of the document related to the event.
  • signatory - Details of the signatory involved in the event, if applicable.
  • organization - Details of the organization related to the event.
  • webhook_data - The full raw webhook payload received from Autentique.

Dependencies

  • Requires an API token credential for Autentique API to validate webhook signatures and optionally to load document options.

Troubleshooting

  • If the webhook signature validation fails, ensure the API token is correctly configured and the webhook headers contain 'x-autentique-signature' and 'x-autentique-timestamp'.
  • If no events are received, verify that the webhook URL is correctly set in Autentique and that the selected event type matches the incoming webhook event.
  • If filtering by specific document IDs, ensure the IDs are correctly formatted and match the documents triggering the webhook.

Discussion