Before you start
To connect Blockz to ENPS you will need:
Access to your Cuez Blockz organization
An NRCS system administrator present, or performing the ENPS-side steps themselves. These steps touch core NRCS configuration.
AP ENPS
Installation order:
Blockz
NRCS MOS gateway configuration (ENPS)
Cuez Automator
Step 1 - Configure the Blockz plugin
1. Log in to your Cuez Blockz organization via blockz.cuez.app (or us.blockz.cuez.app, depending on your region), and log in if prompted.
2. Select the Blockz Repository needed for this installation.
3. Click MOS in the bottom left of the screen. A popup will show up.
4. Fill in the fields:
Field | Description |
NRCS | Select ENPS from the dropdown |
Plugin appearance | Choose light or dark mode for the plugin |
MOS ID | The MOS ID you will set when connecting the Automator (Step 3). Default: |
Default MOS channel | Set per your NRCS configuration |
Cue Block Placement | Set per your production workflow |
Auto-Load Cue block on Story change | When switching stories in ENPS, automatically navigate to the first Blockz MOS object in that story |
Auto-update rundown on edit | Automatically update the MOS object when the plugin data changes |
5. Fill in all fields, then click Create API Key. Copy the URL shown in the dialog.
Save this: copy the HTML Plugin URL. You need it in Step 2, prefixed with URL=.
Step 2 - Configure Blockz in ENPS
Technical setup: the NRCS system administrator must be present or perform these steps themselves.
2.1 Add the MOS device in ENPS
Open the ENPS System Maintenance application. This is only visible to Administrators, or otherwise available on the server running ENPS.
2.2 Go to MOS Configuration and add a new record
Field | Description | Value |
Address | The MOS ID you will set when connecting the Automator (Step 3) |
|
Description | A clear label for this MOS device, visible to ENPS users | - |
IP/Endpoint | IP address of the Cuez Automator | e.g. |
ActiveX | - |
|
Program | - |
|
Default Settings | Paste the HTML Plugin URL from Step 1, prefixed with |
|
MOS Version | The version of the MOS connection |
|
Auto Create | Send "Auto Create" messages to this MOS device | Checked |
Story Send | Send "Story Send" messages to this device. Required for Prompter text and full story sync | Checked |
Browser Type | Which browser system is used for the plugin | Edge WebView2 |
All other MOS Configuration fields are not required for Blockz. Leave them as-is.
Important: click Save in the bottom right to apply your changes.
2.3 Restart the ENPS server
Search for Internet Information Services (IIS) Manager in Windows Search, then press Restart. Restart the ENPS client afterwards to load the newly configured MOS device and plugin.
Heads up: restarting the ENPS server disconnects active clients. They receive a notification that the primary server is temporarily unavailable.
2.4 Verify the plugin appears in ENPS
Reopen the ENPS client. Right-click the MOS button in the bottom menu and confirm the plugin name (the one entered in the Description field) appears in the list.
Step 3 - Connect the Automator to your NRCS
Download the latest stable or beta build from download.cuez.app.
For the initial Automator installation, see Network requirements below for where to install it.
Pair a new project to the Automator and fill in the fields:
Field | Description |
Name | A recognizable label for this connection in your rundown list |
NRCS | Select ENPS from this dropdown |
MOS Device ID | The name this MOS device uses to identify itself in ENPS. Default: |
Newsroom NCS ID | The identifier your NRCS uses on the MOS connection. Get this from your system administrator or the NRCS settings. |
Newsroom Host | IP address of the ENPS server |
Enable dual-peer failover | Check this box to connect to a backup newsroom on the same ports and fail over automatically when the primary goes down |
Secondary NCS ID | The identifier the buddy NRCS uses on the MOS connection, if using dual-peer failover. Leave blank to reuse the primary Newsroom NCS ID |
Secondary Newsroom Host | IP address of the buddy NRCS server, if using dual-peer failover |
Lower Port | Prefilled: |
Upper Port | Prefilled: |
Blockz Repository | Select your region, e.g. Blockz EU or Blockz US |
Repository ID | Log in to Blockz and copy the ID from the browser address bar |
Repository API Key | In Blockz, go to Settings > API Key (bottom right). Create a new key with a recognizable name (e.g. "Automator") and paste it here |
When all fields are filled in correctly, green checkmarks appear left of each field. Click Submit. The Automator opens the list of all rundowns available via MOS.
Result: Blockz, your NRCS, and the Automator are now connected. Start building automations in the Automator.
Network requirements
Where to install the Automator
The Automator is a small application that runs as a service, in the tray on Windows or the menu bar on Mac. It can be installed on a separate computer, or on the same machine running your playout software (vMix, NewBlue, or similar). Whichever machine you choose, it needs a network position that satisfies two requirements at once:
Reachable from the NRCS MOS Gateway. The Automator talks MOS directly to the ENPS server. Place the Automator on a machine that has clear network access to that server: same subnet, or routed with the required ports open (10540/10541 for MOS, plus any ports you configure in Step 3).
Able to reach the studio devices. Automations only fire if the Automator can talk directly to the devices it controls: vision mixers, graphics systems, cameras, audio, playout. Make sure firewalls and VLANs do not block the Automator from reaching each device's control IP and port.
Requirement | Detail |
Internet connection | Required for the Automator app itself |
Local port | 7070, used to access the Automator GUI (default: |
Media storage | Downloaded media (script and rundown assets) is stored in a location you define: the Automator machine, the playout machine, or separate storage |
When installation is done, open a browser (Chrome preferred) and go to the Automator's IP and port, or click Open GUI. On first run, give the Automator a name, then pair it with your project as described in Step 3.
ENPS troubleshooting
How do I make a rundown MOS active?
Open the Running Order and select MOS Control Active.
Rundown does not appear in the Automator
Check the MOS Story Send status for the rundown in ENPS, and confirm the story is included in the send list.
ENPS does not connect to the Automator
Confirm the MOS configuration (ENPS > System Maintenance > MOS Configuration) has the correct IP address for the Automator.
Plugin does not appear after adding MOS Configuration or MOS Story Send
Restart IIS, then restart the ENPS client. The MOS configured device and plugin will appear.
What producers can do once connected
Once connected, producers can insert Blockz cue blocks into any ENPS story using the plugin.