Actaport
Actions29
- Akten Actions
- Aufgaben Actions
- Benutzer Actions
- Dokumente Actions
- Fristen Actions
- Kollisionsprüfung Actions
- Kontakt Actions
- Notizen Actions
- Rechnungen Actions
- Widervorlagen Actions
Overview
This node integrates with the Actaport API, a cloud-based legal practice management software. Specifically, for the Notizen (Notes) resource and the Get operation, it retrieves a single note associated with a specific legal case. The note is identified by its unique ID within the context of a case defined by a running number and a reference year.
Typical use cases include:
- Fetching detailed information about a particular note attached to a legal case.
- Automating workflows that require accessing notes for review or processing.
- Integrating Actaport notes into other systems or dashboards for consolidated case management.
For example, a law firm could use this node to automatically retrieve notes related to a case when preparing documents or generating reports.
Properties
| Name | Meaning |
|---|---|
| Laufende Nummer | Running number of the case; identifies the specific case in Actaport |
| Bezugsjahr | Reference year of the case; used together with the running number to locate the case |
| Notiz ID | The unique identifier of the note to retrieve |
Output
The node outputs the JSON data returned by the Actaport API for the requested note. This JSON typically contains all details of the note such as title, description/content, type, creation/modification timestamps, and any metadata associated with the note.
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 an HTTP GET request to the endpoint:
/akten/{laufendeNummer}/{bezugsJahr}/notizen/{notizId}where
laufendeNummer,bezugsJahr, andnotizIdare provided as input parameters.
Troubleshooting
- Missing or incorrect IDs: If the running number, reference year, or note ID is incorrect or missing, the API will likely return a 404 Not Found error. Verify these values carefully.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network issues: Check connectivity to the Actaport API endpoint.
- API changes: If the Actaport API changes its endpoints or authentication methods, the node may fail until updated accordingly.
Links and References
- Actaport Official Website
- Actaport API documentation (typically available to customers; check your Actaport account or contact support)