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 interacts with the Actaport API to update an existing contact ("Kontakt") in the Actaport legal practice management system. It allows users to modify various details of a contact, such as name, salutation, type (natural or legal person), addresses, phone numbers, email addresses, and other related information.
Typical use cases include:
- Keeping contact information up-to-date in a legal case management workflow.
- Automating updates to client or partner contact details from external systems.
- Synchronizing contact data between Actaport and other CRM or ERP systems.
For example, you could use this node to update a client's phone number and add a new email address automatically when changes occur in your CRM.
Properties
| Name | Meaning |
|---|---|
| Kontakt ID | The unique identifier of the contact to update (required). |
| Vorname | First name of the contact. |
| Name | Last name of the contact. |
| Anrede | Salutation of the contact (e.g., Mr., Ms.). |
| Typ | Type of contact: either "Natürliche Person" (natural person) or "Juristische Person" (legal entity). |
| Additional Fields | A collection of optional fields to provide more detailed contact information: |
| - Adressen | Multiple addresses with details like street, postal code, city, country, recipient, address type (private/business), house number, and postal address flag. |
| - Akademischer Titel | One or more academic titles associated with the contact. |
| - Ansprechpartner | Contact persons related to this contact, each with an ID and display name. |
| - Bemerkung | Notes or remarks about the contact. |
| - Email Adressen | Multiple email addresses for the contact. |
| - Favorit | Boolean flag indicating if the contact is marked as a favorite. |
| - Faxnummern | Multiple fax numbers with value and type (private/business). |
| - Geburtsdatum | Birth date of the contact. |
| - Gesetzliche Vertreter | Legal representatives of the contact, each with a type (e.g., Vorstand, Geschäftsführer, Bevollmächtigter) and linked contact ID and display name. |
| - Kontoverbindungen | Bank account connections including IBAN, BIC, account holder, and bank name. |
| - Rechtsform | Legal form of the contact (string). |
| - Telefonnummern | Multiple phone numbers with value and type (private, business, mobile). |
Output
The node outputs the JSON response returned by the Actaport API after updating the contact. This typically includes the updated contact object with all its properties reflecting the changes made.
No binary data output is involved.
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 uses HTTP PUT requests to update contacts at the endpoint
/kontakte/{kontaktId}.
Troubleshooting
- Missing Kontakt ID: The update operation requires a valid contact ID. If omitted or incorrect, the API will return an error indicating the contact was not found.
- Invalid field values: Providing invalid formats for fields like dates, emails, or enumerations (e.g., contact type) may cause validation errors from the API.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network issues: Connectivity problems to the Actaport API endpoint can cause request failures.
- Partial updates: Fields not provided will remain unchanged; ensure all intended fields are included in the update payload.
To resolve errors, verify input parameters, check API credentials, and consult Actaport API documentation for field requirements.
Links and References
- Actaport Official Website
- Actaport API documentation (not publicly linked here; refer to your Actaport developer resources)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls