ADVBOX icon

ADVBOX

Consume ADVBOX API

Actions8

Overview

This node interacts with the ADVBOX API to retrieve the movement history related to a specific lawsuit. It is useful for legal professionals or case managers who need to track all movements (actions, updates, or changes) associated with a lawsuit over time. For example, a user can fetch the latest 10 movements of a lawsuit to monitor its progress or audit recent activities.

Properties

Name Meaning
Lawsuit ID The unique identifier of the lawsuit for which the movement history will be retrieved.
Additional Fields Optional parameters to customize the response:
- Limit: Number of items to return (1-100).
- Offset: Number of items to skip before starting the response (for pagination).

Output

The output is a JSON array where each element represents a movement record associated with the specified lawsuit. Each movement typically includes details such as date, description, and other metadata provided by the ADVBOX API.

If the node encounters an error during the request, the output may contain an object with an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the ADVBOX API.
  • The node makes HTTP requests to the ADVBOX API endpoints.
  • The API base URL and token are obtained from the configured credentials.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Common Issues:

    • Missing or invalid API token: The node will throw an error if the authentication token is not found or invalid.
    • Network issues or API downtime can cause request failures.
    • Providing an incorrect Lawsuit ID will result in no data or an error response from the API.
  • Error Messages:

    • "Token de autenticação não encontrado. Verifique suas credenciais."
      Means the API token is missing; verify that the API key credential is correctly configured.
    • Errors like "Erro ao obter histórico de movimentos: <message>" indicate problems fetching the movement history, possibly due to network issues, invalid parameters, or API errors.
  • Resolution Tips:

    • Ensure the API key credential is set up properly in n8n.
    • Verify the Lawsuit ID is correct and exists in the ADVBOX system.
    • Check network connectivity and API service status.
    • Use the Limit and Offset fields carefully to avoid requesting too many records at once.

Links and References

Discussion