Select CXOne Mpower in workflow
Pick CXOne Mpower app in the workflow builder [4] - just one click to select the app.
Triggers can detect changes in CXOne Mpower and run actions that can create, search or modify data inside CXOne Mpower automatically [3] — exactly how you set them.
3 simple steps to make your CXOne Mpower connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
Pick CXOne Mpower app in the workflow builder [4] - just one click to select the app.
When prompted, authorize access to CXOne Mpower in WEXTL once. CXOne Mpower credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your CXOne Mpower account. Approve?
Build your workflow with CXOne Mpower yourself or with WEXTL® AI Builder. Connect CXOne Mpower to any available integrations [5], or use HTTP node to go beyond them.
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever CXOne Mpower app is called in workflows. That allows your communication automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that CXOne Mpower supports.
The following table illustrates what fields CXOne Mpower integration require during authorization flow inside our workflow builder [4].

Video slide demonstrates how CXOne Mpower is connected in WEXTL builder [4].
| Field | Type | Help |
|---|---|---|
CXone Mpower - Environment (Issuer)Required | select | Select the issuer environment used for OAuth2 authentication. This value is used for the token request to |
CXone Mpower - Client IDRequired | text | The OAuth2 |
CXone Mpower - Client SecretRequired | password | The OAuth2 |
CXone Mpower - Access Key IDRequired | text | The Access Key ID generated from a CXone Mpower user account. Sent as |
CXone Mpower - Access Key SecretRequired | password | The Access Key Secret generated alongside the Access Key ID. Sent as |
| CXone Mpower – Station ID | text | Station ID used to start an agent session. Either this or Station Phone Number is required. |
| CXone Mpower – Station Phone Number | text | Agent phone number used to start an agent session. Either this or Station ID is required. |
| CXone Mpower – Inactivity Timeout (seconds) | number | Idle timeout between 30–300 seconds. Default is 300. |
| CXone Mpower – Force Logout on Inactivity | boolean | If true, session ends after inactivity regardless of agent state. |
| CXone Mpower – Impersonate Agent ID | number | Starts the session as another agent. Requires Impersonate Agent permission. |
Enter a name of the other app you want to sync with CXOne Mpower below. Click on selected app to explore integration options with CXOne Mpower. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Select Watch Contacts trigger from CXOne Mpower - this will be a starting point in your automation. Whenever event happens in CXOne Mpower, workflow will start [7] from Watch Contacts node.
Search for Add a Chat Contact, connect it as the next step of integration sequence. You can use filters between Watch Contacts and Add a Chat Contact, so only important data pass from Watch Contacts to the next step. WEXTL gives you full control over the process of CXOne Mpower automation. All parts of workflow are visible on the canvas [4].
CXOne Mpower on WEXTL has 120 modules for combining communication automations. Explore CXOne Mpower documentation for more.

Video slide demonstrates how Watch Contacts and Add a Chat Contact [6] nodes are used in CXOne Mpower workflow.
Common questions about automating CXOne Mpower in your workflows.
List of sources used to gather information about the CXOne Mpower integration.