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 Managements by ACW
AI-generatedOverview
This node interacts with the Beex Contact Center API to retrieve reports related to managements by After Call Work (ACW). It is useful for obtaining detailed ACW typing reports filtered by portfolio, date range, and optionally by user. This can help in analyzing post-call activities and agent performance in a contact center environment.
Use Case Examples
- Retrieve ACW management reports for a specific campaign portfolio within a date range.
- Filter ACW management reports by user ID to analyze individual agent post-call work.
Properties
| Name | Meaning |
|---|---|
| Portfolio ID | ID of the campaign to filter the report, obtained from the Campaigns module on the platform. |
| Start Date | Start date for filtering the report data, in YYYY-MM-DD format. |
| End Date | End date for filtering the report data, in YYYY-MM-DD format. |
| User ID | Optional ID of the user who logged the typing, to filter the report by specific user. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Number of results to return if Return All is false. |
| Offset | Page number to obtain, starting from 0, for paginated results. |
Output
JSON
json- The JSON output contains the ACW management report data retrieved from the Beex API.
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 Beex API. Ensure all required fields like Portfolio ID, Start Date, and End Date are correctly set.
- API authentication errors may occur if the API key credential is missing or invalid. Verify the API key is correctly configured in the node credentials.
- Rate limiting or request throttling may happen due to the 1-second delay between requests implemented in the node. Adjust usage accordingly.
Links
- Beex Contact Center API Documentation - Official API documentation for understanding available endpoints and parameters.