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, specifically providing functionality to retrieve conflict checks ("Kollisionsprüfung"). The "Get" operation under the "Kollisionsprüfung" resource allows users to search for conflict checks by name and supports pagination.
Typical use cases include:
- Legal professionals or law firms wanting to verify potential conflicts of interest by searching existing conflict checks.
- Automating conflict check lookups in workflows where case or client data is processed.
- Retrieving paginated lists of conflict checks filtered by a specific name pattern.
For example, a user can input a partial or full name to find matching conflict checks and control the number of results per page and which page to retrieve.
Properties
| Name | Meaning |
|---|---|
| Name | Name to search for in conflict checks (string). This filters the conflict checks by the given name. |
| Page | Zero-based page index (number). Specifies which page of results to return, starting at 0. |
| Size | The size of the page to be returned (number). Defines how many conflict check entries are returned per page. |
Output
The node outputs JSON data representing the retrieved conflict checks from the Actaport API. The structure corresponds to the API's response for conflict checks, typically including details such as conflict check identifiers, names, and related metadata.
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 GET requests to the
/kollisionspruefungendpoint with query parameters for filtering and pagination.
Troubleshooting
- Empty Results: If no conflict checks are returned, verify that the "Name" parameter matches existing records or try broadening the search criteria.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Pagination Issues: Confirm that the "Page" and "Size" parameters are within valid ranges; negative values or excessively large sizes may cause errors.
- API Connectivity: Network issues or incorrect base URL configuration can prevent successful API calls.
Links and References
- Actaport Official Website
- Actaport API documentation (not publicly linked here; refer to your Actaport account or developer resources)