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 and related entities such as customers, tasks, movements, settings, and transactions. Specifically, for the Lawsuit - Get by id operation, it retrieves detailed information about a single lawsuit using its unique identifier.
Typical use cases include:
- Fetching detailed lawsuit information for case management workflows.
- Integrating lawsuit data into other systems or dashboards.
- Automating updates or notifications based on lawsuit status.
For example, a user can input a lawsuit ID to retrieve all relevant details about that case, such as involved parties, stages, types, and notes, enabling further processing or reporting within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Lawsuit ID | The unique identifier of the lawsuit to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the lawsuit details fetched from the Advbox API. The structure typically includes fields such as:
users_id: ID of the user responsible for the lawsuit.customers_id: Array of customer IDs associated with the lawsuit.stages_id: ID of the current stage of the lawsuit.type_lawsuits_id: ID of the lawsuit type.- Additional optional fields like process number, protocol number, folder, date, and notes if available.
The output is a JSON object containing all relevant lawsuit information as returned by the Advbox API. There is no binary data output in this operation.
Dependencies
- Requires an API key credential for authenticating with the Advbox API.
- The node expects the Advbox API base URL and token to be configured in the credentials.
- No additional external dependencies are needed beyond the Advbox API access.
Troubleshooting
- Missing or invalid API token: The node will throw an error if the API token is not provided or invalid. Ensure the API key credential is correctly set up.
- Invalid or missing Lawsuit ID: If the provided lawsuit ID does not exist or is malformed, the API may return an error or empty response. Verify the lawsuit ID before running the node.
- Network or API errors: Temporary network issues or API downtime can cause request failures. The node logs requests and errors; retrying after some time or checking API status may help.
- Permission errors: If the API token lacks permissions to access lawsuit data, the node will fail. Confirm that the API key has appropriate rights.
Links and References
- Advbox API Documentation (general reference for endpoints and data structures)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices
This summary focuses on the "Lawsuit" resource with the "Get by id" operation, describing how the node fetches lawsuit details by ID through the Advbox API.