Actions18
Overview
The node integrates with the Autentique API to manage digital documents and their signatures. Specifically, the "Send via WhatsApp Flow" operation allows sending a document through a WhatsApp messaging flow to a specified phone number. This is useful for automating the delivery of documents that require signature or review via WhatsApp, leveraging the popular messaging platform for faster and more direct communication.
Practical examples:
- Sending contracts or agreements directly to clients' WhatsApp numbers for quick signing.
- Delivering invoices or receipts via WhatsApp as part of an automated workflow.
- Notifying signatories about pending documents through WhatsApp flows with customized data.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to be sent via WhatsApp. |
| Phone Number | The recipient's phone number in international format (e.g., +5511999999999). |
| Flow Data | Optional additional JSON data to customize the WhatsApp Flow message or behavior. |
Output
The output JSON contains details of the document after the WhatsApp flow send action, including:
id: Document identifier.name: Document name.signatures: An array of signature objects related to the document, each containing:public_id: Public identifier of the signature.name: Name of the signer.phone: Phone number associated with the signature.
This output confirms the document was processed and provides updated signature information. The node does not output binary data.
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 the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Invalid Document ID: If the provided document ID does not exist or is incorrect, the API will return an error. Verify the document ID before running the node.
- Incorrect Phone Number Format: The phone number must be in international format (e.g., +5511999999999). Invalid formats may cause the API to reject the request.
- API Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Empty or Malformed Flow Data: If providing custom flow data, ensure it is valid JSON; otherwise, the API might reject the request.
- Network Issues: Connectivity problems can cause request failures; verify network access to the Autentique API endpoint.
Links and References
- Autentique API Documentation (general reference for API capabilities)
- WhatsApp Business API documentation (for understanding WhatsApp flow concepts, external to Autentique)
This summary is based on static analysis of the node's source code and property definitions for the "Document" resource and "Send via WhatsApp Flow" operation.