ADVBOX icon

ADVBOX

Consume ADVBOX API

Actions8

Overview

This node integrates with the ADVBOX API to manage legal case movements. Specifically, the Movement - Create operation allows users to create a new manual movement entry related to a lawsuit. This is useful for legal professionals or case managers who want to log updates, events, or procedural steps in a lawsuit directly from their workflow automation.

Typical use cases include:

  • Logging court dates, filings, or other procedural movements in a lawsuit.
  • Automating the tracking of case progress by creating movement records when triggered by external events.
  • Centralizing lawsuit updates within an automated workflow system.

Example: Automatically create a movement record with a description and date whenever a new event occurs in a case management system.

Properties

Name Meaning
Lawsuit ID The identifier of the lawsuit (legal case) to which this movement relates.
Data do Movimento (Date) The date of the movement in the format DD/MM/YYYY.
Descrição (Description) A textual description detailing the nature or content of the movement.

Output

The node outputs JSON data representing the created movement as returned by the ADVBOX API. This typically includes details such as the movement's ID, associated lawsuit ID, date, description, timestamps, and any other metadata provided by the API.

No binary data output is involved.

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.
  • Network access to the ADVBOX API endpoint is necessary.

Troubleshooting

  • Authentication errors: If the API token is missing or invalid, requests will fail. Ensure that the API key credential is correctly set up and active.
  • Invalid date format: The date property must be in DD/MM/YYYY format. Providing an incorrect format may cause the API to reject the request.
  • Missing required fields: All three properties (lawsuit_id, date, description) are mandatory. Omitting any will result in an error.
  • API request failures: Network issues or API downtime can cause request errors. Check connectivity and ADVBOX service status.
  • Error messages: Errors thrown by the node include descriptive messages from the API or internal validation. Review these messages to identify the cause.

Links and References

Discussion