Notifications
Post newsroom events to a Slack channel or Google Chat space, choosing the events and newsdesks each destination follows.
The Notifications tab posts newsroom events to your team chat. You add a destination, a Slack channel or a Google Chat space, and each destination picks its own events and newsdesks. This page is the steps; what each message contains is in Slack and Google Chat.
Who can use it
Owners and admins (notification:manage). There is no read-only view: the tab is missing for Members and
Viewers.
Turn notifications on
Use the Enable notifications switch at the top. While it is on, "Destinations below receive the events they subscribe to." While it is off, nothing is sent and your destinations are kept. You see Notifications enabled or Notifications disabled. The switch is unavailable while a destination is open for editing.
Add a destination
- Under Destinations, choose Add destination.
- Under Send to, choose Slack or Google Chat.
- Fill in the form:
- Name: how the destination appears in Nuvelics, for example the channel or space name. Required, up to 80 characters.
- Incoming Webhook URL for Slack, an
https://hooks.slack.com/address, or Webhook URL for Google Chat, anhttps://chat.googleapis.com/address. Each webhook posts to the one channel or space it was created for. For Google Chat, create the webhook from the space's Apps & integrations in the Google Chat web app; it needs a Business or Enterprise Google Workspace. - Events: pick at least one of New pitch, Story enriched and Pushed to NRCS. For New pitch, set a minimum score from 40 to 100; it starts at 70. At 40 the destination gets every pitch except a manual pitch scored below 40.
- Newsdesks: All newsdesks, which includes ones created later, or Selected newsdesks with the desks you pick. Choosing selected desks and picking none is refused: Pick at least one newsdesk, or choose All newsdesks.
- Optional but recommended: choose Send test message. You see Test message sent. if the chat service accepted it, or The test message was not accepted with the reason if not. Too many tests in a few minutes are refused until you wait.
- Choose Save.
You see Destination added. The webhook URL is write-only: once saved it is never shown again.
A URL that is not the right kind is refused: Enter a Slack Incoming Webhook URL (https://hooks.slack.com/…) or Enter a Google Chat webhook URL (https://chat.googleapis.com/…).
Read the list
Each destination shows its name, medium, the events it follows, the minimum score where it applies, and its newsdesks: All newsdesks, a list with "+ more", or No newsdesks selected — nothing is posted if the selection is empty. A newsdesk that no longer exists is counted as not found.
Edit a destination
- Choose the pencil button beside it (its name is Edit followed by the destination's name). Only one destination can be open at a time: "Finish or cancel the open destination to edit another."
- Change the name, events, score or newsdesks. To change the webhook, paste a new address into Replace webhook URL; leave it blank to keep the saved one. A new URL is tested before it replaces the old one. The medium cannot be changed on an existing destination.
- Choose Save.
You see Destination saved. If another person saved first you are told "This destination changed since you loaded it — reload and try again."
Fix a destination that stopped working
When the chat service refuses a message, the destination is badged Not working and says "This webhook no longer works. Replace its URL to resume posting." Paste a new webhook URL in Replace webhook URL and save to resume.
Remove a destination
- Open the destination for editing and choose Remove destination.
- Confirm Remove destination. This removes the destination and its saved webhook, and nothing more is posted to it.
You see Destination removed.
Other ways to manage notifications
- API: Notifications.