Actions14
- Customer Actions
- Lawsuit Actions
- Task Actions
- Movement Actions
- Transaction Actions
Overview
This node integrates with the Advbox API to manage legal case (lawsuit) data. Specifically, the Update Lawsuit operation allows users to modify details of an existing lawsuit record in the Advbox system. This is useful for legal professionals or administrative staff who need to keep lawsuit information current, such as updating the responsible user, stage, type, process number, protocol number, folder, date, or notes related to a lawsuit.
Practical examples include:
- Changing the assigned user responsible for a lawsuit.
- Updating the current stage or type of the lawsuit as it progresses.
- Correcting or adding missing process or protocol numbers.
- Adding notes or changing the folder designation for organizational purposes.
- Adjusting the date associated with the lawsuit.
Properties
| Name | Meaning |
|---|---|
| Lawsuit ID | The unique identifier of the lawsuit to update. |
| Update Fields | Collection of fields to update on the lawsuit. Possible fields: |
| - User ID: Identifier of the user responsible for the lawsuit. | |
| - Stage ID: Identifier of the current stage of the lawsuit. | |
| - Lawsuit Type ID: Identifier of the lawsuit type. | |
| - Process Number: Official process number of the lawsuit. | |
| - Protocol Number: Protocol number associated with the lawsuit. | |
| - Folder: Folder name or identifier where the lawsuit is stored. | |
| - Date: Date related to the lawsuit, formatted as DD/MM/YYYY. | |
| - Notes: Additional textual notes about the lawsuit. |
Output
The node outputs JSON data representing the updated lawsuit object returned by the Advbox API after the update operation. The structure corresponds to the lawsuit resource with updated fields reflecting the changes made.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Advbox API.
- Needs the base URL of the Advbox API configured in the credentials.
- The node uses HTTP requests to communicate with the Advbox API endpoints.
- No additional external dependencies beyond the Advbox API and n8n's HTTP request capabilities.
Troubleshooting
- Missing or invalid API token: The node will throw an error if the API token is not provided or invalid. Ensure that the API key credential is correctly set up.
- Invalid API URL: If the API base URL is missing or incorrect, the request will fail. Verify the URL in the credentials.
- Invalid Lawsuit ID: Providing a non-existent or malformed lawsuit ID will result in an error from the API. Confirm the lawsuit ID before updating.
- Empty update fields: If no fields are provided to update, the API may reject the request or perform no action. Always specify at least one field to update.
- Date format errors: The date field must be in
DD/MM/YYYYformat; otherwise, the API might reject the input. - API request failures: Network issues or API downtime can cause request failures. Check connectivity and Advbox service status.
- Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.
Links and References
- Advbox API Documentation (Assumed, replace with actual link if available)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide
If you need further details on other operations or resources, feel free to ask!