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
Relation → Create
AI-generatedOverview
This node operation creates a relation between specified parent and child entities within the onOffice system. It is useful for linking different records such as estates, appointments, addresses, or other entities by defining their relationship type and additional relation information. For example, it can be used to associate an estate with multiple contact persons or link an address to a calendar event.
Use Case Examples
- Creating a relation between an estate (parent) and multiple addresses (children) to define contact persons.
- Linking an appointment (parent) with addresses (children) for scheduling purposes.
Properties
| Name | Meaning |
|---|---|
| Parent IDs | Comma-separated list of parent entity IDs to which the relation applies (e.g., estate IDs, appointment IDs). |
| Child IDs | Comma-separated list of child entity IDs to be related to the parents (e.g., address IDs). |
| Relation Type | Type of relation to establish between the parent and child entities, selected from predefined options representing different relation contexts. |
| Relation Info | Additional information about the relation, such as appointment confirmation status. |
Output
JSON
relationId- Identifier of the created relation.status- Status of the relation creation operation.
Dependencies
- Requires an API key credential for onOffice API authentication.
Troubleshooting
- Ensure that the parentIds and childIds are provided as comma-separated strings and correspond to valid existing entities in the onOffice system.
- Verify that the selected relation type is appropriate for the entities being linked.
- Check API credentials and permissions if the node fails to authenticate or perform the operation.
- Common errors may include invalid IDs, missing required fields, or unauthorized access, which can be resolved by validating inputs and credentials.