Actions7
- Document Actions
- Template Actions
Overview
This node, named "DocuGenerate," integrates with the DocuGenerate API to manage documents and templates. Specifically, for the Delete Document operation, it allows users to delete a document by specifying its unique document ID. This is useful in workflows where document lifecycle management is required, such as removing outdated or incorrect documents automatically after processing or archiving.
Practical examples include:
- Automatically deleting a generated PDF document after sending it via email.
- Cleaning up test or temporary documents created during workflow execution.
- Managing document storage by removing documents that are no longer needed.
Properties
| Name | Meaning |
|---|---|
| Document ID | The ID of the document to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will be a confirmation response from the API indicating whether the deletion was successful. The exact structure depends on the API but usually includes status information or an empty object if the deletion succeeded.
No binary data output is expected for this operation.
Dependencies
- Requires an API key credential for authenticating with the DocuGenerate API.
- The node makes HTTP requests to
https://api.docugenerate.com. - Proper configuration of the API key credential within n8n is necessary for successful authentication.
Troubleshooting
Common issues:
- Invalid or missing Document ID: Ensure the Document ID provided exists and is correct.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Check connectivity and the status of the DocuGenerate service.
Common error messages:
- Unauthorized or 401 errors: Indicate invalid API credentials; reconfigure the API key.
- 404 Not Found: The specified Document ID does not exist; verify the ID.
- 400 Bad Request: Possibly due to malformed input; ensure the Document ID is properly formatted.
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring network connectivity.
Links and References
- DocuGenerate API Documentation (for detailed API endpoints and responses)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)