Autentique Trigger icon

Autentique Trigger

Recebe notificações de eventos da Autentique via webhook

Overview

This node acts as a webhook trigger for receiving event notifications from the Autentique platform, which is used for managing digital document signing workflows. It listens for specific events related to documents and signatories, such as when a document is created, signed, rejected, or when a particular signatory signs or rejects a document.

Common scenarios where this node is beneficial include:

  • Automating follow-up actions after a document is fully signed (e.g., sending confirmation emails or updating CRM records).
  • Tracking document lifecycle events in real-time.
  • Filtering notifications to only process events related to specific documents.
  • Validating incoming webhook requests to ensure they originate from Autentique.

Practical example: A user can configure this node to trigger a workflow whenever a document is fully signed (document_signed event). The workflow could then download the signed document, archive it, and notify relevant stakeholders automatically.

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 to only specific documents (boolean).
IDs Dos Documentos Comma-separated list of document IDs to filter by. Only used if "Apenas Documentos Específicos" is true. Leave empty to accept all documents.
Validar Assinatura Whether to validate the webhook signature using the API token (boolean). Ensures webhook authenticity.

Output

The node outputs JSON data containing details about the received event. The structure includes:

  • event: The type of event received (e.g., document_signed).
  • timestamp: The timestamp of the event; if not provided by the webhook, the current time is used.
  • document: An object with information about the document involved in the event.
  • signatory: An object with information about the signatory involved, if applicable.
  • organization: An object with organization-related data.
  • webhook_data: The full raw webhook payload as received.

Example output JSON snippet:

{
  "event": "document_signed",
  "timestamp": "2024-06-01T12:00:00Z",
  "document": { /* document details */ },
  "signatory": { /* signatory details */ },
  "organization": { /* organization details */ },
  "webhook_data": { /* full webhook payload */ }
}

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Autentique API.
  • The node expects to be configured with a valid webhook URL on the Autentique platform to receive event notifications.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Missing or invalid webhook signature: If the "Validar Assinatura" property is enabled, the node expects specific headers (x-autentique-signature and x-autentique-timestamp) in the webhook request. Missing these will cause an error indicating an invalid signature. To resolve, ensure that the Autentique webhook is correctly configured to send these headers and that the API token used matches.

  • Event type mismatch: If the node is configured to listen for a specific event but receives a different one, it will ignore the webhook and respond with a status 200 but indicate the event was ignored. Verify the event selection matches the expected webhook events.

  • Document filtering issues: When filtering by specific document IDs, if the incoming event's document ID is not in the list, the webhook is ignored. Ensure the document IDs are correctly entered, comma-separated without extra spaces.

  • API errors when loading documents: The node uses a GraphQL query to fetch documents for dropdown options. Errors here usually relate to invalid credentials or network issues. Check API key validity and network connectivity.

Links and References

Discussion