Skip to content

Skip repeat news events before writing posts in Kotia

Set up Skip repeats to filter out news events you have already processed. Configure comparison rules, edit the saved list, and retry after a failed run.

Updated

Exclude events you have already processed before parsing and writing new posts. "Skip repeats" compares the incoming selection with its own history and passes on only what counts as new under your rules. This way, you can run a news channel without preparing the same event again from different sources.

The service compares the meaning of materials, not just headlines and link addresses. You can specify which updates deserve a separate post, and you can edit the saved list. The history records that a material passed the filter. An entry does not mean that the post was published successfully.

How to tell a repeat from a follow-up

Two links about the same product launch can count as a repeat — but test results published later are a new development of the same story. You set this difference in the instructions: say what your readers are no longer interested in and what deserves a separate post.

The saved list is available for viewing and editing. You can add events that you have already covered yourself, or delete one entry to process a news item again. This way, you control the selection without resetting the entire history.

Where to place the card

Connect the filter to a step that passes material for checking: text, a list, or a document. A connection from "Start" alone is not enough, because it does not pass any data for comparison.

For news, the usual order is:

Search → select relevant events → "Skip repeats" → read sources → write → result.

If you select five events from a large set of results, place "Skip repeats" after this selection. Otherwise, more news items will end up in the list of processed events than you planned to use.

What is remembered: material that passed through the filter. An entry in the list does not mean that a post has already been written or published. Those actions happen later.

You can take a fully configured chain from the workflow "News for a Telegram channel".

How to set up a comparison rule

  1. Add "Skip repeats" and connect the input to the step you need.
  2. Open the card settings.
  3. For a standard check, leave the "Brief" empty. The service will filter out anything already in the list.
  4. If it is important to tell a repeat of an event from its follow-up, describe the criteria in the brief. The card is not only for news: in the brief you can name what identifies a repeat, such as "match by the contact's email" for a list of companies or "one story in different outlets is a repeat".
  5. Connect the output to further processing and check the result of the first run.

An example for a news channel:

Treat messages about the same event as a repeat, even if the headline and the outlet are different. Let new developments through: a decision that has been made, published results, changed conditions, or confirmed new figures. Keep the headline, date, and link of each new material.

With this rule, you do not rewrite one press release based on articles from different media outlets, and you do not lose a meaningful follow-up to the story.

Incoming material What should happen under this rule
Another outlet reported the same product launch The repeat is filtered out
Only the headline of a known news story changed The repeat is filtered out
Test results were published after the announcement The material passes as a new development
Another news item on the same broad topic appeared The material passes if the event is new

This is a semantic check performed with AI. During the first runs, compare the result with your expectations and refine the rule using examples typical of your topic.

What happens on the first and later runs

If the saved list is empty, the card passes the incoming material through and records it. On the next run, the card compares the new data with the accumulated list, filters out what it already knows, and adds whatever passes to the list.

The card splits what comes in into separate records — news stories, companies, contacts — and picks a short identifier for each one using the rule in the brief. Only that identifier goes into the "already done" list, while the whole record moves on with all its details. If the brief is empty, the card picks the identifier itself. So if a repeat should be recognised by something specific — an email, a website address, a company name — say so in the brief.

The list is saved between runs of the same card. Inside a loop, all passes use the same memory: material that passed in the first pass is taken into account in the second pass.

How to view and edit the saved list

The settings have a "List — already done" field. Each item is written on a new line. This is the memory content that the service uses for the next check.

  1. Open the settings for "Skip repeats."
  2. Find the event you need in the list.
  3. Delete a line if you want to make the event eligible for processing again, or add an event that you have already covered outside this workflow.
  4. Click "Save list." List changes are saved only with this button.

When you save, the entire edited list is written. Empty lines and exact duplicates are removed. For several events, add a separate line for each one, so they are easier to read and correct.

Clearing the memory makes all earlier materials eligible for processing again. To process a single news item again, it is usually enough to delete only its entry. A copy of the card starts with empty memory. If it needs the previous list, transfer it manually and save it.

If there are no new events

When the filter removes all materials, the dependent branch is skipped: the next step on the canvas turns grey with the label "no task arrived" and uses no tokens. This is a normal result of regular monitoring, not a failure: there are currently no suitable new materials. Independent branches of the workflow can continue to run.

Do not ask the filter to output the phrase "no news" instead of an empty result. The next step may treat it as material for a post. If the document is at the end, check the current run: text saved earlier may still be in the document.

If a news item was remembered but no post was created

For example, the filter passed an event, but an error occurred when the page was read the next time. The event has already been recorded in memory, so when you run the whole workflow again, the filter may remove it.

Open "Runs" and find where the run stopped. If the previous result has been saved, use a partial run from the step you need. If you need to go through the search and the filter again, delete the specific entry from memory and save the list.

If the card's response was cut off, the memory is not updated, so you do not need to fix the list manually. Shorten the task or the amount of input data and run the check again.

Cost and memory maintenance

The charge for the check depends on the model work actually performed. Each run uses the incoming material, the brief, and the saved list. The longer the memory, the more processing it requires. For a large list, the panel will show a warning.

Keep enough detail to tell events apart, but remove unnecessary long retellings. Delete old events deliberately: after deletion, they can pass the filter again. Each pass in a loop is a separate check with its own usage.

Situation What to do
Different links to the same event pass again Specify in the brief that events should be compared, not addresses
The filter removes important follow-ups Describe the signs of a new development and check whether the entries in memory are too general
Old events repeat in a copy of the workflow Check the list of the new card: copying does not transfer memory
Manual list edits did not affect the result Make sure you clicked "Save list" before the next run

For permanent information about your company or audience, use a different card: "Memory". "Skip repeats" solves a specific task: it prevents you from processing again anything that has already passed through this filter.