"Interrupt the music for something else" sounds like one requirement. It is actually three, and they need different tools.
Fixed time, automatic: the clock wheel
Network news at exactly :00. Nobody is in the building and it must happen regardless.
Use a clock wheel slot with a stream URL pointed at the feed, restricted to the relevant hours. It fires at the minute you set, with a two-second debounce so it cannot double-fire within the same minute.
This is the only option that works unattended, because it depends on wall-clock time rather than on where the playlist happens to be.
Approximate time, with a person: a cue stop
A live interview around 09:15, once the current song finishes.
Place a cue stop after the appropriate row. Playback stops there instead of advancing, and — importantly — the engine does not preload the following track, so nothing is already crossfading in when the stop lands.
The operator does the segment and presses play. The next track is already selected.
Right now, reactive: a jingle button
A breaking news sounder, a caller sounder, a goal.
Fire a jingle button, or the numpad key mapped to it. Music ducks to 50% automatically and restores when the jingle finishes. Nothing about the playlist changes.
Choosing wrongly
The common mistakes are worth naming.
Using a cue stop for something that must happen at a fixed time means it happens whenever the preceding song ends — which could be two minutes late.
Using a clock wheel slot for something needing a human means it fires into an empty studio.
Using a playlist item for a reactive sounder means finding and starting a row while live, which is exactly what jingle buttons exist to avoid.
Combining them
A typical top of the hour uses all three: the wheel fires the news relay at :00, a cue stop hands over to the presenter afterwards, and a jingle button covers whatever happens in between.