Actions58
- Address Actions
- Agentslog Actions
- Appointment Actions
- E-Mail Actions
- Estate Actions
- File Actions
- Relation Actions
- Search Criterion Actions
- Setting Actions
- Task Actions
- Template Actions
Estate → Get Tenant Buyer Seeker
AI-generatedOverview
This node interacts with the OnOffice API to retrieve tenant, buyer, or seeker information related to real estate data. It is useful for scenarios where users need to match or find tenant, buyer, or seeker details based on specific estate data such as postal code or city. For example, a real estate agent could use this node to find potential tenants or buyers interested in properties within a certain area.
Use Case Examples
- Retrieve tenant or buyer information for a property in Aachen using postal code 52074.
- Match tenant or buyer seekers based on estate data provided as a JSON object.
Properties
| Name | Meaning |
|---|---|
| Estate Data | A JSON object containing estate data used for matching tenant, buyer, or seeker information (e.g., {"plz": "52074", "ort": "Aachen"}) |
Output
JSON
tenantBuyerSeekerData- The matched tenant, buyer, or seeker information retrieved from the OnOffice API based on the provided estate data
Dependencies
- Requires an API key credential for OnOffice API authentication to access estate-related data.
Troubleshooting
- Ensure the JSON object for estate data is correctly formatted and contains valid keys such as postal code (plz) and city (ort).
- Check that the OnOffice API credentials are correctly configured and have the necessary permissions.
- Common errors may include authentication failures, invalid JSON input, or no matching tenant/buyer/seeker data found. Verify input data and API connectivity.
Links
- OnOffice API Documentation - Official documentation for the OnOffice API, useful for understanding available endpoints and data structures.