Actaport
Actions29
- Akten Actions
- Aufgaben Actions
- Benutzer Actions
- Dokumente Actions
- Fristen Actions
- Kollisionsprüfung Actions
- Kontakt Actions
- Notizen Actions
- Rechnungen Actions
- Widervorlagen Actions
Overview
The node integrates with the Actaport API, a cloud-based legal practice management software. Specifically, for the Akten (cases) resource and the Update operation, this node updates an existing case identified by its running number and reference year.
This is useful in scenarios where you need to programmatically modify details of a legal case stored in Actaport, such as updating case metadata or other attributes managed by the API. For example, you might update case status, add notes, or change associated data fields as part of an automated workflow that synchronizes case information from other systems or triggers updates based on external events.
Properties
| Name | Meaning |
|---|---|
| Laufende Nummer | Running number of the case. This uniquely identifies the case within the given year. |
| Bezugsjahr | Reference year of the case. Used together with the running number to identify the case. |
These two properties are required to specify which case to update.
Output
The output of the node will be the JSON response returned by the Actaport API after performing the update operation on the specified case. This typically includes the updated case data reflecting the changes made.
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 API must be configured in the credentials.
- The node sends HTTP PUT requests to the endpoint
/akten/{laufendeNummer}/{bezugsJahr}to perform the update.
Troubleshooting
- Invalid Case Identification: If the combination of running number and reference year does not correspond to an existing case, the API may return a "not found" error. Ensure these values are correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Validation Errors: If the update payload is missing required fields or contains invalid data, the API may reject the request. Check the API documentation for required fields when updating cases.
- Network Issues: Connectivity problems can prevent successful API calls. Confirm network access to the Actaport API endpoint.
Links and References
- Actaport Official Website
- Actaport API documentation (not publicly linked here; consult your Actaport account or support for API docs)