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, the "Notizen" (Notes) resource's "Update" operation allows users to update an existing note associated with a legal case. This is useful for legal professionals who need to modify details of notes linked to cases, such as correcting information or adding new content.
Typical scenarios include:
- Updating the title or description of a note attached to a case.
- Changing the type of a note if applicable (though currently only one type is supported).
- Keeping case documentation accurate and up-to-date within automated workflows.
Example: A user wants to update the description of a note related to a specific case identified by its running number and reference year.
Properties
| Name | Meaning |
|---|---|
| Laufende Nummer | Running number of the case to which the note belongs. |
| Bezugsjahr | Reference year of the case. |
| Notiz ID | The unique identifier of the note to be updated. |
| Titel | Title of the note. |
| Beschreibung | Description or content of the note. |
| Notiz Typ | Type of the note. Currently, only "Aktennotiz" (case note) is supported. |
Output
The node outputs the JSON response from the Actaport API after updating the note. This typically includes the updated note's data reflecting the changes made, such as the new title, description, and type.
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 Actaport API endpoint corresponding to the note update.
Troubleshooting
- Missing Required Fields: Ensure that all required properties (
laufendeNummer,bezugsJahr,notizId,titel,beschreibung) are provided; otherwise, the API will reject the request. - Invalid Note ID: If the
notizIddoes not exist or is incorrect, the API will return an error indicating the note was not found. - Authentication Errors: Verify that the API key credential is valid and has sufficient permissions.
- API Endpoint Issues: Confirm that the base URL is correctly set in the credentials and that the Actaport API service is reachable.
- Unsupported Note Type: Currently, only the "Aktennotiz" type is supported; using other types may cause errors.
Links and References
- Actaport Official Website
- Actaport API Documentation (if publicly available)
- n8n Documentation on HTTP Request Node for understanding API interactions