NRCS

The NRCS tab records how Nuvelics reaches your newsroom computer system. A connection is what lets a story you push from Nuvelics land in your newsroom system, and what lets that system send stories and feeds back. This page is the steps; what a Saga connection does is in Saga newsroom system, and pushing a story is in Push a story to your newsroom.

Who can use itCopy Anchor Link

Owners and admins (nrcs:manage). The tab is missing for Members and Viewers.

Add a connectionCopy Anchor Link

Today Saga is the one system you can connect. The picker also lists Storydesk, Ross Inception, AP ENPS, SNews Arion, Octopus and CGI OpenMedia, each marked Coming soon and not selectable.

1. Choose Add connection.
2. In Add NRCS connection, choose Saga.
3. On Connect Saga, fill in the form:
   • Name: how the connection appears in Nuvelics, for example "Production Saga".
   • API URL: Saga's API host. https only.
   • Instance URL: your hosted Saga instance. https only.
   • API key: your Saga API key. It is stored encrypted, and Nuvelics never shows it again. Use Show API key to check what you typed before you save.
4. Choose Add connection.

You see NRCS connection added and the connection joins the list, showing its System, Name and Health. A blank field is refused (for example Name is required or API key is required), and a URL that is not https is refused with Enter a valid https URL.

Check a connection's healthCopy Anchor Link

Each connection shows a Health of Healthy, Unhealthy or Unknown. It reflects how the connection's credential has fared when Nuvelics used it. A connection nothing has used yet is Unknown and says "No delivery has exercised this connection yet." There is no separate test button.

Edit a connectionCopy Anchor Link

1. Open the connection from the list.
2. Change Name, API URL or Instance URL.
3. To replace the key, type the new one in Replace API key. Leave it blank to keep the current key. If you change the API URL to another server you must enter the key again, and are told Re-enter the API key to move the connection to another server if you do not.
4. Choose Save changes.

You see NRCS connection saved. If another person saved first you are told "This connection changed since you loaded it — reload and try again."

The same screen holds the three optional behaviours below. They are saved with Save changes; if the connection saves but one of them does not, the page says which part landed and which did not, for example "Connection saved. Webhook couldn't be saved" with the reason.

Accept deliveries from Saga (Webhook)Copy Anchor Link

Turn on Accept inbound deliveries from Saga to let Saga push stories to Nuvelics. When you save, Nuvelics generates an Endpoint URL and an API key for Saga to use. The key is shown once; copy both into Saga's own settings at that point with Copy to clipboard, because "Nuvelics won't show it again". While the switch is off, Saga cannot deliver to this connection, and the endpoint and key are kept, so turning it back on reuses them.

To rotate, choose Regenerate. Rotating replaces both the endpoint URL and the key, so Saga must be updated with both. The current key stays live until you save, and Cancel rotation backs out before then.

Evaluate delivered stories (Skills)Copy Anchor Link

Under Skills, turn on Evaluate stories Saga delivers against the org's story checks. While it is on, every matching story Saga delivers is evaluated; stories delivered before you switched it on are not changed. The checks are the ones under Story checks.

Deliver pitches to Saga (Pitch feed)Copy Anchor Link

Under Pitch feed, turn on Deliver pitches to Saga's feed intake, then map each newsdesk to a Saga feed:

1. Choose Add mapping.
2. Pick a Newsdesk and enter its Saga feed id. The id must match exactly, so remove any leading or trailing space.
3. Choose Save changes.

If the feed is on but no newsdesk is mapped, a warning says nothing will be delivered until at least one is. Use a mapping's menu to Edit it or Delete it; removing one stops that newsdesk delivering to its feed, and pitches already delivered stay in the newsroom.

Copy the HTML plugin URLCopy Anchor Link

Above the list, HTML Plugin shows an address for your organization with a copy button. It appears whether or not you have connections yet. What the plugin does, and where the address goes, is covered under Use Nuvelics inside Saga.

Delete a connectionCopy Anchor Link

1. Open the connection's NRCS connection actions menu, or the connection page, and choose Delete.
2. Confirm in Delete NRCS connection. This deletes the connection and the API key stored for it, and Nuvelics can no longer reach the system.

You see NRCS connection deleted. If a data source still uses the connection's credential, the delete is refused and names that data source; detach or replace the credential on it first.

Other ways to manage connectionsCopy Anchor Link

• CLI: nuvelics nrcs-config.
• API: NRCS configs.
• An AI assistant can list connections and push stories with the NRCS tools.