Sources
A source defines where Signailist gets materials: public feeds, channels and chats, or your own system through the API. Combine different sources in one workspace and choose publication destinations independently.
Choose a source
| Source | What you need | What Signailist collects |
|---|---|---|
| Telegram | A connected account with access to the channel or chat | Messages from the selected channel or chat |
| RSS / Atom | A public HTTPS feed URL | Entries available in the feed, with original article links |
| GitHub Releases / Steam / YouTube | Public repository, AppID or channel ID | Releases, game news or video entries; see limitations below |
| Your own system | API key with ingest or an MCP connection | Versioned text materials submitted to a private source |
Owner and Editor roles can configure sources. Viewers can inspect saved materials.
RSS and Atom feeds
RSS and Atom are website news feeds. Enter the feed URL, rather than the website's home page or the URL of a single article. Both formats use the same RSS source option.
You do not need an API key, a Telegram account or your own server for a public feed.
- Open Sources, choose RSS and enter a public HTTPS feed URL.
- Save the source. A new source starts paused.
- Enable collection and choose Collect now. Collection runs in the background and may take a few minutes. Check the last collection time and saved entries.
- Connect the source to an active topic. For the initial entries, choose Prepare saved entries for AI. Saving the initial feed preview does not start AI analysis or publish anything.
- Check the entries and their topic scores in the feed, then use them in a digest.
The initial preview contains up to 20 entries. RSS provides only entries still present in the feed; it cannot restore an article that the website has already removed from that feed. A saved entry retains its original article link and the content supplied by the feed; a feed may contain an excerpt rather than the full article.
Wait for the first saved entries before pausing a new source. Re-enabling collection follows new entries and does not repeat the initial history.
GitHub Releases, Steam and YouTube
Choose a dedicated option in Sources → Add source. Signailist converts your input to a public feed and shows its address before you save. These sources do not require API keys or a Telegram account.
| Option | Accepted input | What is collected |
|---|---|---|
| GitHub Releases | facebook/react or https://github.com/facebook/react | Published releases and their release notes; commits and issues are not included |
| Steam | AppID such as 108600 or https://store.steampowered.com/app/108600/ | News and update announcements published in the game's feed; this is not a download or installed-version monitor |
| YouTube | Channel ID such as UC_x5XG1OV2P6uZZ5FSM9Ttw or https://www.youtube.com/channel/UC_x5XG1OV2P6uZZ5FSM9Ttw | Recent video titles, descriptions, thumbnails and video links; videos and transcripts are not downloaded |
For YouTube, use the channel's UC… ID or /channel/… URL. A video link or an @handle URL is not accepted. You can copy a channel ID from YouTube's channel sharing options. An existing feed URL also works for each option.
If YouTube collection fails, open the feed address to check whether the feed is available. If it is temporarily unavailable, retry collection later.
When the YouTube feed returns 404, Signailist tries the channel’s public Videos page. This mode can provide only the title, thumbnail and video link, without a description; Shorts and stream archives are not collected separately. If the exact publication time is unavailable, the saved entry uses its discovery time. If the public page is also unavailable, collection reports an error and can be retried later.
After saving, enable collection, collect entries, connect a topic and prepare the saved entries for AI, as described above. These options use the same feed collection, topic analysis, digest editor and publication destinations as RSS/Atom. They start paused. Adding the same feed again reuses the existing source.
Availability and history depend on the public feed: only the entries it currently contains can be collected. Private repositories and restricted content are not supported by these options.
YouTube channel names and Steam game names are filled in automatically when available. Your own source name is preserved. If the service cannot load a name, it temporarily shows the channel or game ID; a later successful collection can update it.
Collection, source name lookups and saving feed entries use the workspace balance, even when the external feed is free. See Balance and usage.
Telegram channels and chats
- Connect a Telegram account and enable its collection role. See Telegram integration.
- Open Sources, choose Telegram and add a public channel by username or select a channel or chat available to the connected account.
- Enable collection and check the saved messages in the feed.
- Connect the source to an active topic to evaluate incoming news against your interests.
The connected account must already have access to private channels and chats.
Your own materials through API or MCP
Create a private external source and submit text materials individually or in batches. Each item has an external identifier, version, title, text and publication time. Repeating the same version creates no new processing job or intake charge; changed text requires a new version.
This source receives pushes from your system and does not poll it on a schedule. Saved materials enter the shared processing workflow for analysis and digests. Check jobs and AI readiness separately from the intake receipt. See the intake and webhook guide for contracts and examples.
Analysis and digests
Collected and externally submitted materials use the same topic scoring and digest workflow. You can select processed materials from different sources for one digest. AI analysis and generation use the selected workspace's settings and balance. See AI.
Choose the publication destinations later, in the digest's Publication tab. See Delivery channels.
Pause collection
Pause a source to stop collecting new materials from it. Saved materials remain available. Source collection and recurring digest schedules are controlled separately: pausing a schedule does not pause its sources.