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 interacts with the Actaport API, specifically focusing on managing reminders ("Widervorlagen") related to legal cases. The "Update Status" operation for the "Widervorlagen" resource allows users to update the status of a specific reminder associated with a case identified by its running number and reference year.
This operation is useful in scenarios where reminders need to be marked as either open or completed, helping legal professionals keep track of pending and resolved tasks or follow-ups within their case management workflow.
Practical example:
A law firm uses this node to automatically mark a reminder as "Erledigt" (completed) once a related task is finished, ensuring that the case's reminder list stays current without manual updates.
Properties
| Name | Meaning |
|---|---|
| Laufende Nummer | Running number of the case to which the reminder belongs. |
| Bezugsjahr | Reference year of the case. |
| Wiedervorlage ID | The unique identifier of the reminder to update. |
| Status | New status for the reminder. Options: "Offen" (open), "Erledigt" (completed). |
Output
The node outputs JSON data representing the updated reminder object returned from the Actaport API after the status change. This typically includes details such as the reminder's ID, associated case information, new status, and other metadata.
No binary data output is involved in 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.
- Internet access to reach the Actaport cloud service.
Troubleshooting
Common issues:
- Incorrect or missing case running number or reference year may cause the API request to fail or return not found errors.
- Providing an invalid or non-existent reminder ID will result in failure to update the status.
- Network connectivity problems or incorrect API credentials can lead to authentication errors.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly set up and valid.
- 404 Not Found: Verify that the case identifiers (running number and reference year) and reminder ID are correct.
- 400 Bad Request: Ensure the status value is one of the allowed options ("OFFEN" or "ERLEDIGT").
Links and References
- Actaport API Documentation (general reference for API endpoints and usage)
- n8n Documentation (for general guidance on using n8n nodes and credentials)