Purpose
This guide explains how to dynamically replace the outbound Caller ID using Pure CallerID’s Aegis API inside the new Mpower Flow Designer, without relying on legacy skills or scripts.
Prerequisites
- Access to Flow Designer
- An available Outbound Flow or Campaign Flow
- Aegis API Key and Workflow ID
- Your outbound calls must respect contact.ani if overridden
Step-by-Step Integration
- Create or Open a Flow
Navigate to Flow Designer and open or create an Outbound or Campaign Flow. - Add a Webhook Block
Method: GET
URL:
https://aegis.purecallerid.app/api/public/aegis?workflow-id=YOUR_WORKFLOW_ID&to={{contact.phone}}&from={{contact.ani}}&zip={{contact.zip}}&format=json&X-API-KEY=YOUR_API_KEY
Save Response As: aegisResponse - Add a Set Variables Block
Set: contact.ani = aegisResponse.pcidFromNumber
This overrides the ANI for the outbound leg. - Continue the Flow
Proceed to the Dial, Queue, or Contact destination block.
Ensure your outbound system respects the contact.ani override.
Legacy Tenant Note
If your tenant still has access to legacy CXone Studio skills and the ACD Admin interface, and you're currently using Studio scripts for outbound pre-call logic, refer to the legacy method described in the companion article:
"Integrating Aegis with NICE CXone Using Studio Scripts (Legacy Method)"
That guide provides step-by-step instructions on using a Rest Api Action block and script-level ANI overrides in environments that predate Mpower's Flow Designer architecture.
Example Flow
Start
→ Webhook (Call Aegis)
→ Set Variables (contact.ani = Aegis ANI)
→ Outbound Call Routing
Testing
Inject test contacts into the flow.
Use debug logging or tools to verify the value returned in aegisResponse.
Limitations
- Requires your outbound carrier or CXone config to accept dynamic ANI from contact.ani
- Requires Flow Designer to be enabled for your tenant