ADVBOX

Overview

This node integrates with the Advbox API to manage legal case movements and other related resources. Specifically, for the Movement resource with the Get history operation, it retrieves the movement history of a specified lawsuit. This is useful for legal professionals or case managers who want to track all recorded movements (events or updates) associated with a particular lawsuit.

Typical use cases include:

• Auditing the timeline of actions taken on a lawsuit.
• Generating reports on lawsuit progress.
• Monitoring manual or court-originated movements for compliance or review.

For example, you can input a lawsuit ID and optionally filter by the origin of movements (court or manual), then get a detailed list of all movements related to that lawsuit.

Properties

Name	Meaning
Lawsuit ID	The unique identifier of the lawsuit for which to retrieve the movement history.
Additional Fields	Optional filters for the request. Currently supports: - Origem (origin): Filter movements by their origin, either "Tribunal" (court) or "Manual".

Output

The output is a JSON array containing objects representing individual movements related to the specified lawsuit. Each object typically includes details such as date, description, origin, and other metadata about each movement event.

No binary data is output by this operation.

Example output structure (simplified):

[
  {
    "id": "movement_id",
    "lawsuit_id": "12345",
    "date": "2023-01-15",
    "description": "Movement description",
    "origin": "tribunal"
  },
  ...
]

Dependencies

• Requires an API key credential for authenticating with the Advbox API.
• The node uses the Advbox API base URL and token configured in the credentials.
• No additional external dependencies are required 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 your credentials are correctly set up with a valid API key.
• Invalid lawsuit ID: If the lawsuit ID does not exist or is malformed, the API may return an error or empty results. Verify the lawsuit ID before running the node.
• Network or API errors: Temporary network issues or Advbox API downtime can cause request failures. The node logs errors and retries some requests internally but persistent failures should be checked.
• Filtering by origin: If filtering by origin yields no results, verify that the origin value matches exactly ("tribunal" or "manual") and that such movements exist for the lawsuit.

Links and References

• Advbox API Documentation (general reference; actual URL may vary)
• n8n documentation on creating custom nodes
• Legal case management best practices for tracking lawsuit movements

---

This summary focuses exclusively on the Movement > Get history operation as requested, based on static analysis of the provided source code and property definitions.