Actions59
- Blacklist Actions
- Call Actions
- Client Actions
- Entity Actions
- Import Actions
- Lead Actions
- PBX Actions
- Queue Actions
- Report Actions
- Get Daily Managements
- Get Dropped Calls
- Get Summary
- Get Time Slot
- Get Users Management
- Get Calls
- Get Client Management
- Get Forms
- Get Incoming Call
- Get IVR Survey
- Get Log ACW
- Get Managements by ACW
- Get Managements per Hour
- Get Messaging Tickets
- Get PDP Control
- Get List PDP
- Get PDP Ranking
- Get Phones
- Get Platform Detailed
- Get Platform Summarized
- Get Product Managements
- Get Products
- Get Progress Managements
- Get Strategies
- Get Tickets Tracking
- Sequence Actions
- Template Actions
- Ticket Actions
- User Actions
Report → Get Log ACW
AI-generatedOverview
This node operation fetches the ACW (After Call Work) log typing report from the Beex Contact Center API. It is useful for retrieving detailed logs of ACW activities filtered by campaign (portfolio), company, date range, and optionally by user. This can help in monitoring and analyzing post-call work activities in a contact center environment.
Use Case Examples
- Retrieve ACW log entries for a specific campaign and company within a date range.
- Filter ACW logs by a specific user to analyze individual performance.
Properties
| Name | Meaning |
|---|---|
| Portfolio ID | ID of the campaign to filter the ACW log data, obtained from the Campaigns module on the platform. |
| Start Date | Start date for filtering the ACW log entries, in YYYY-MM-DD format. |
| End Date | End date for filtering the ACW log entries, in YYYY-MM-DD format. |
| Company ID | ID of the company for which the ACW log data is retrieved. |
| User ID | Optional ID of the user who logged the typing, to filter the ACW log data by user. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return if Return All is false. |
| Offset | Page number to obtain, in descending order by creation date, starting from 0. |
Output
JSON
json- ACW log entries returned from the Beex API, each entry representing a log record.
Dependencies
- Beex Contact Center API with an API key credential
Troubleshooting
- Common errors include invalid or missing parameters, which result in error messages from the API. Verify that all required fields such as Portfolio ID, Company ID, Start Date, and End Date are correctly set.
- API authentication errors may occur if the API key credential is missing or invalid. Ensure the API key is correctly configured in the node credentials.
- Rate limiting or network errors may cause request failures. The node includes a delay between requests to mitigate rate limits, but network stability should be checked.
Links
- Beex API Documentation - Log ACW Report - Official API documentation for the Log ACW report endpoint.