Actions19
Overview
This node integrates with the Autentique API to create a new digital document for signature workflows. It allows users to upload a document file (in Base64 format), specify signatories with their roles and actions, and configure various signing options such as signature order, reminders, deadlines, and signature styles.
Common scenarios where this node is beneficial include automating contract signing processes, managing approval workflows, and digitally collecting signatures on legal or business documents. For example, a company can use this node to send a service agreement PDF to multiple stakeholders for sequential signing with customized email messages and automatic reminders.
Properties
| Name | Meaning |
|---|---|
| Document Name | The name/title of the document being created (e.g., "Service Agreement"). |
| File Content (Base64) | The content of the document file encoded in Base64. Supported formats include PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, ODT, ODS, ODP, RTF, HTML, TXT. Maximum size: 20MB. Use a file reading node to convert files to Base64. |
| Signatures | JSON array defining the signatories. Each entry must include name, email, and action which can be one of SIGN, APPROVE, SIGN_AS_A_WITNESS, or RECOGNIZE. Example: [{"name": "João Silva", "email": "joao@exemplo.com", "action": "SIGN"}]. |
| Refusable | Boolean indicating if the document can be refused by signatories. |
| Sortable | Boolean indicating if signatures must follow a specific order (sequential signing). |
| Message | Custom message sent via email to all signatories. |
| Reminder | Frequency of automatic reminders sent to signatories. Options: None, Daily, Weekly. |
| Footer Position | Position of the footer on the document. Options: None, Bottom, Left, Right. |
| Qualified Signature | Boolean to enable qualified digital signatures using certificates. |
| Scrolling Required | Boolean indicating if signatories must scroll through the entire document before signing. |
| Stop on Rejected | Boolean indicating if signing should stop for other signatories when the document is refused. |
| New Signature Style | Boolean to enable new signature field styles. |
| Show Audit Page | Boolean to show an audit page at the end of the document summarizing the signing process. |
| Ignore CPF | Boolean to remove the requirement for signatories to fill in CPF (Brazilian tax ID) when signing. |
| Ignore Birthdate | Boolean to remove the requirement for signatories to fill in birthdate. |
| Deadline | ISO 8601 datetime string specifying the deadline for completing all signatures. |
| Organization ID | Optional ID of the organization under which the document will be created. |
| Folder ID | Optional ID of the folder where the document will be stored. |
Output
The node outputs JSON data representing the newly created document, including its unique identifier and metadata returned from the Autentique API. This typically includes:
- Document ID
- Document name
- Status and creation timestamps
- List of signatures with their public IDs, names, emails, actions, and links for signing
No binary output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Autentique API.
- The node sends requests to the Autentique API endpoint at
https://api.autentique.com.br/v2. - To provide the document content, users often need to use a file reading node to convert files into Base64 format before passing it to this node.
Troubleshooting
- File Size Limit Exceeded: If the Base64 file content exceeds 20MB, the API will reject the request. Ensure the file size is within limits.
- Invalid Signatures JSON: The signatures property must be a valid JSON array with required fields (
name,email,action). Malformed JSON or missing fields will cause errors. - Missing Required Fields: Omitting required properties like
fileContentorsignatureswill result in validation errors. - Authentication Errors: Ensure the API key credential is correctly configured and has permissions to create documents.
- Deadline Format Issues: The deadline must be in ISO 8601 format; otherwise, the API may reject the request.
- Unsupported File Formats: Only certain file types are supported; uploading unsupported formats will fail.
Links and References
- Autentique API Documentation (for detailed API usage and schema)
- n8n Documentation - Working with Credentials
- Base64 Encoding Guide