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 → Read
AI-generatedOverview
This node reads entries from the Agentslog resource in the onOffice system. It allows users to retrieve specific log data related to agents' activities, filtered and sorted according to various parameters. This is useful for scenarios where detailed tracking and analysis of agent logs are needed, such as monitoring agent performance, auditing actions, or generating reports based on agent activities.
Use Case Examples
- Retrieve agent log entries filtered by specific parameters like 'Aktionsart' or 'Datum'.
- Fetch a limited number of agent log records with sorting applied to analyze recent activities.
- Use filter rules to get entries within a date range or matching certain action types.
Properties
| Name | Meaning |
|---|---|
| Parameters | Select specific fields from the Agentslog entries to be returned, such as 'Absagegrund', 'Adress_nr', 'Aktionsart', etc. |
| Additional Fields | Additional optional parameters to refine the query and control the output, including filters, limits, sorting, and specific IDs. |
Output
JSON
Absagegrund- Reason for cancellation in the log entryAdress_nr- Address number associated with the log entryAktionsart- Type of action recordedAktionstyp- Subtype of the actionBemerkung- Remarks or comments related to the log entryBenutzer- User associated with the log entryBenutzer_nr- User numberBeratungsebene- Consultation level of the log entrycreated- Timestamp when the log entry was createdDatum- Date of the log entryDatum_bearb- Date when the log entry was processed or editeddauer- Duration related to the log entryHerkunftKontakt- Origin of the contact in the log entryKosten- Costs associated with the log entrymerkmal- Feature or characteristic of the log entryObjekt_nr- Object number associated with the log entry
Dependencies
- An API key credential for onOffice API authentication
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to access Agentslog data.
- Verify that the filter rules and parameters are correctly formatted, especially for operators like IN and BETWEEN which require comma-separated values.
- Check the list limit and offset values to avoid requesting too many records or invalid pagination.
- If sorting by fields, ensure the JSON format for 'Sort By' is valid or use the 'Sort Order' option correctly.
- Common error messages may include authentication failures, invalid parameter formats, or exceeding API rate limits. Resolving these involves checking credentials, input formats, and API usage limits.
Links
- onOffice API Documentation - Official API documentation for onOffice, useful for understanding available endpoints and parameters.