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
Agentslog → Create
AI-generatedOverview
This node operation creates a new agents log entry in the onOffice system. It is useful for tracking and recording various actions or events related to agents, such as appointments, tasks, or other activities. Users can specify detailed information about the log entry, including action type, advisory level, linked entities (like addresses, estates, projects), timing, duration, costs, and notes.
Use Case Examples
- Creating a log entry for a support call with details about the action type and duration.
- Logging an appointment with linked estate and user information.
- Recording a cancellation with a reason and advisory level G.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to provide detailed information about the agents log entry, such as action kind, action type, linked IDs, advisory level, date and time, duration, costs, notes, and user ID. |
Output
JSON
id- ID of the created agents log entryactionkind- Kind of action recordedactiontype- Type of action recordedaddressids- Linked address IDsadvisorylevel- Advisory level of the log entryappointmentid- Linked appointment IDcost- Costs associated with the log entrydatetime- Date and time of the log entryduration- Duration in secondsestateid- Linked estate IDfeatures- Features or characteristics linked to the log entryfileids- Linked file IDsnote- Notes or remarksorigincontact- Type of contactprojectid- Linked project IDreasoncancellation- Reason for cancellation if advisory level is Gtaskid- Linked task IDuserid- User ID for support or logged in user if not set
Dependencies
- An API key credential for onOffice API authentication
Troubleshooting
- Ensure all required fields are correctly formatted, especially date and time in 'Y-m-d H:i:s' format.
- If linking IDs (address, estate, project, etc.), verify that these IDs exist in the onOffice system.
- Advisory level G requires a reason for cancellation; omitting this may cause errors.
- If user ID is not set, the node uses the logged-in user; ensure the credential has appropriate permissions.