Actaport icon

Actaport

Interact with Actaport API. Actaport is a cloud-based legal practice management software that provides digital law office tools for case management, communication, and practice administration.
Join our community

Actions29

Overview

The node integrates with the Actaport API, a cloud-based legal practice management software. Specifically, for the Akten (Cases) resource and the Get operation, it retrieves detailed information about a specific legal case identified by its running number and reference year.

This node is beneficial in scenarios where you need to fetch case details programmatically within an automation workflow, such as:

  • Retrieving case data to display or process further in a legal firm's internal systems.
  • Integrating case information into document generation or reporting tools.
  • Synchronizing case details with other applications like CRM or billing systems.

Example use case: Given a case's running number "12345" and reference year "2025", the node fetches all associated data from Actaport for that case, enabling downstream nodes to utilize this information.

Properties

Name Meaning
Laufende Nummer Running number of the case; uniquely identifies the case within the given year.
Bezugsjahr Reference year of the case; used together with the running number to identify the case.

Output

The node outputs JSON data representing the full details of the requested case as returned by the Actaport API. This typically includes all metadata and attributes related to the case, such as parties involved, status, dates, and any other case-specific information stored in Actaport.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Actaport API.
  • The base URL for the Actaport API must be configured in the node credentials.
  • The node sends a GET request to the endpoint /akten/{laufendeNummer}/{bezugsJahr} to retrieve case data.

Troubleshooting

  • Common issues:

    • Incorrect or missing running number or reference year will result in failure to find the case.
    • Invalid or expired API credentials will cause authentication errors.
    • Network connectivity issues may prevent reaching the Actaport API.

  • Error messages:

    • 404 Not Found: The specified case does not exist. Verify the running number and reference year.
    • 401 Unauthorized: Authentication failed. Check the API key credential configuration.
    • 400 Bad Request: Input parameters might be malformed or missing. Ensure required fields are provided.

Resolving these usually involves verifying input values, checking API credentials, and ensuring network access to the Actaport service.

Links and References

  • Actaport Official Website
  • Actaport API documentation (not publicly linked here; consult your Actaport account or support for API docs)

Discussion