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 resource and the Get Many operation, it retrieves multiple case records (legal cases) from Actaport in a paginated manner.
This operation is useful when you want to fetch a list of cases for further processing, reporting, or automation workflows within n8n. For example, you might use this node to:
- Retrieve all active legal cases for review.
- Fetch cases page by page to synchronize with another system.
- Automate notifications or updates based on case data.
Properties
| Name | Meaning |
|---|---|
| Page | Zero-based index of the page to retrieve (0..N). Determines which subset of cases to fetch. |
| Size | Number of cases to return per page. Controls the page size for pagination. |
These properties allow control over pagination when fetching many cases.
Output
The node outputs JSON data representing the retrieved cases from Actaport. The structure corresponds to the API response for multiple cases, typically including an array of case objects with their details such as case number, year, status, and other 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 Actaport API must be configured in the credentials.
- The node sends HTTP GET requests to the
/aktenendpoint with query parameterspageandsize.
Troubleshooting
- Empty results: If no cases are returned, verify that the page and size parameters are set correctly and that there are cases available in the account.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- API rate limits: Large page sizes or frequent requests may hit API limits; reduce page size or add delays.
- Incorrect base URL: Confirm the base URL in credentials matches the Actaport API endpoint.
Links and References
- Actaport Official Website
- Actaport API documentation (not publicly linked here; refer to your Actaport account or support for API docs)