TelematicTelematic
How it worksFeaturesDemoPricingBlogChannels
Sign inTry it freeSign in
How it worksFeaturesDemoPricingBlogChannels
TelematicTelematic

AI content automation: collect, adapt and publish on schedule.

Solutions

  • Faceless YouTube automation
  • Text to video for Shorts & TikTok
  • Blog to video
  • Telegram channel autoposting
  • For YouTube automation agencies
  • Pricing
  • Telegram post generator
  • Partner program

Contacts

  • Our Telegram channel
  • Telegram Support
  • Email Support

Help

  • About
  • Docs
  • FAQ
  • Blog

Legal Information

  • Terms of Use
  • Public Offer
  • Privacy Policy
  • Created by Webula
Copyright Β© 2025 β€” 2026Telematic.Pro
    1. Home
    2. Knowledge Base
    3. Content sources: where the system gets its topics
    Back to Help
    July 19, 20262 views

    Content sources: where the system gets its topics

    Seven source types, step-by-step setup, a test run and scheduled collection, automatic acceptance of items, prices and common errors.

    A source is a place Telematic takes material for posts from: a channel, a website, an RSS feed, YouTube or the AI itself. Here you will choose a type, check the source and turn on collection on a schedule. It takes 5–10 minutes, and collection costs from 1 token per item.

    Choose a source type

    The AI rewrites every collected item in your project's style right away β€” that is included in the price. The original is kept alongside.

    TypeWhen it fitsPrice
    "Telegram channel"A public channel. One new post per run1 token per item
    "Website (scraper)"A site or blog with no RSS. From 1 to 50 articles per run1 per item
    "RSS feed"The site has RSS. One new article in full per run1 per item
    "YouTube channel"The channel's videos become text, 1–10 per run1 per minute of video; an already transcribed video β€” 1
    "Fixed URL"One page that keeps changing: rates, weather, listings1 per item
    "AI generator"The AI writes an item from your descriptionfrom 1 (depends on the model)
    "AI Aggregator"Digests made from the project's accepted and published items1 per issue

    Important. "YouTube channel" is closed during the trial period (the "Not available during trial access" badge) and opens after your first top-up.

    Add a source

    1. Open your project and choose "Sources" in the menu on the left.
    2. Click "Add source" and click the card you need in the "Choose source type" window.
    3. Fill in the only field, "Source Name", and click "Create".
    4. The source page opens. The source is already active, but it has no schedule β€” it will not start collecting on its own yet.

    The seven source types; YouTube is marked as unavailable during the trial period

    Set up collection

    On the "Settings" tab the fields save themselves: wait for the "Saved" mark at the top. Only the Telegram channel name and the YouTube channel address are saved with the "Save" button.

    • Telegram. Type "Channel username" without the @, save and click "Test". Only public channels work.
    • Website. Enter the address and click "Fill automatically": the AI will find the links to articles and the text on the page, free of charge. If the site has RSS, the service will tell you β€” a feed is more reliable.
    • RSS and fixed URL. The address and the "Test" button are all you need.
    • YouTube. The channel address, "Max minutes per video" (0 means the whole video) and "Max videos per run".
    • AI generator. Describe the topic in the "AI instructions" block. One run makes one item; the AI sees the last 10 headlines and picks a new topic. The "Don't fabricate things that didn't happen" toggle adds a fact check.
    • Aggregator. Choose "Output type" (digest, roundup, timeline), set the filters and click "Check filters".

    For the other types the "AI instructions" block sets the tone of the rewrite. The "Presets" button opens "Template presets": click a template and the fields fill themselves in.

    After autofill the selector fields are filled in, with examples of the articles that will be collected below

    Check the source with a test run

    1. In the "Test run" block click "Run" β€” the price is shown on the button itself.
    2. The run's progress appears line by line under the button β€” wait for it to finish.
    3. In the "Collected Content" list each item has three actions:
      • "Create draft" β€” the item appears in the project's content as a draft;
      • "Reject" β€” it is saved as rejected and will not be collected again;
      • "Remove" β€” this only hides it: next time the item is collected and paid for again.

    Important. A test run charges tokens like any other run, but nothing reaches your content without the "Create draft" button. The project filter, auto-accept and auto-analysis take no part in a test.

    What it costs. The price is charged per item, not per run. A run that finds no new items costs 1 token (except for YouTube).

    Collection results: what the source found and what AI turned it into

    Turn on collection on a schedule

    1. On the "Automation" tab choose "Run interval" β€” from 5 minutes to 30 days.
    2. In the "Operational Window" block set the hours when collection is allowed, for example "Working day (9–18)".
    3. In the "Collected materials handling" block turn on what you need:
      • "Auto-accept content from automated runs" β€” items are accepted immediately and a version of the post is created for every connected platform (from 1 token per platform, depends on the model);
      • "Auto-analyze collected content" β€” 1 token per item. Set the "Accept when importance β‰₯" and "Reject when importance ≀" thresholds: anything between them stays a draft;
      • "Reject content without media".
    4. Click "Enable automation". The first run happens after one full interval, not straight away.

    The source schedule: the interval, the window and the three toggles for handling items

    Without those toggles, everything collected becomes a draft. Topics you do not want are cut off by the project filter (the three-dot menu on the project page β†’ "Content filter"): by stop words, free of charge; by meaning, 1 token per item.

    Important. There are two pauses: one on the source itself (the button on its card in the list) and one on the schedule ("Pause"). Scheduled collection only runs when both are active. A test run works even while paused.

    Keep an eye on the run log

    The "Journal" tab shows the last 10 runs; the shared "Runs log" tab in the source list shows 5 for each source.

    • "Success" β€” items were collected, with the count next to it.
    • "Idle run" β€” there are no new items.
    • "Skipped" β€” there were not enough tokens. This does not count as an error.
    • "Failed" β€” open the line to read why.

    The source log: a successful run expanded, with one skipped for balance below it

    Duplicates and old items

    • Telegram, website and RSS sources skip a link the project already has in any status. So it is better to reject what you do not need than to delete it.
    • A fixed URL creates a new item on every run, even if the page has not changed. The AI generator, the aggregator and YouTube do not check for repeats either.
    • Drafts you never touch are rejected automatically after a while, rejected ones go to the archive, and the archive is deleted along with its files. Each step takes 30 days by default; you can change the periods in the project menu β†’ "Content retention".
    • "Delete" wipes the schedule and the log. The items already collected stay in the project.

    If something goes wrong

    What you seeWhat to do
    The run button is greyWait for the "Saved" mark
    The site is unavailable, no links foundThe site is closed to robots or requires a login. Try its RSS feed
    The Telegram channel is not foundCheck the name without the @ and make sure the channel is public
    "Out of tokens β€” top up to resume"After three skips in a row the schedule pauses, and it resumes by itself once you top up
    "Not configured"Five errors in a row. Fix the settings and click "Edit" β†’ "Save"

    What next

    • Working with content β€” how to check drafts and prepare posts.
    • Publications and calendar β€” how accepted items go out to your platforms.
    • Autopilot β€” the whole cycle with no manual steps.
    • Tokens and payment β€” every price in one place.
    • Choose a source type
    • Add a source
    • Set up collection
    • Check the source with a test run
    • Turn on collection on a schedule
    • Keep an eye on the run log
    • Duplicates and old items
    • If something goes wrong
    • What next
    Previous article

    Working with content: from draft to finished post

    Next article

    Projects and platforms: Telegram, YouTube, VK, TikTok and your website