Actions18
Overview
The node integrates with the Autentique API to manage digital documents for electronic signatures. Specifically, the Search operation under the Document resource allows users to search for documents using advanced filters such as search terms, document status, folder filtering, pagination, and sorting options.
This node is beneficial in scenarios where you need to programmatically retrieve a filtered list of documents from your Autentique account, for example:
- Finding all pending signature documents containing a specific keyword.
- Retrieving recently updated signed contracts within a particular folder.
- Paginating through large sets of documents while applying custom sorting.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return (minimum 1). |
| Page | Page number of the results (minimum 1). |
| Search Term | Text to search for in the document name. |
| Document Status | Filter by document status. Options: All, Draft, Expired, Pending, Rejected, Signed. |
| Search Folder ID | Optional folder ID to filter documents by folder. |
| Order By | Field to order results by. Options: Created At, Updated At, Name. |
| Order Direction | Direction of ordering. Options: Descending, Ascending. |
Output
The output JSON contains a paginated list of documents matching the search criteria. Each document object includes:
id: Document identifier.name: Document name.refusable: Boolean indicating if the document can be refused.sortable: Boolean indicating if signatures must follow a specific order.created_at: Creation timestamp.updated_at: Last update timestamp.status: Current status of the document.signatures: Array of signature objects, each with:public_id,name,email,created_ataction(withname)userinfo (id,name,email)
folder: Object with folderidandname.
Additionally, pagination metadata is included:
total: Total number of matching documents.per_page: Number of documents per page.current_page: Current page number.last_page: Last available page number.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Autentique API.
- The node makes HTTP POST requests to the Autentique GraphQL endpoint at
https://api.autentique.com.br/v2/graphql. - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Empty Results: If no documents are returned, verify that the search term, status, and folder filters are correct and that documents exist matching those criteria.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Invalid Pagination: Providing a page number beyond the last page will result in empty data; adjust the page parameter accordingly.
- API Rate Limits: Excessive requests may trigger rate limiting; implement delays or reduce request frequency.
- Malformed Input: Ensure numeric fields like
limitandpageare positive integers.
Links and References
- Autentique API Documentation (general reference, actual URL may vary)
- GraphQL Queries and Mutations
- n8n Documentation on Creating Custom Nodes