Source Blocks#
Source blocks are the entry points for data into your workflow. They connect to external platforms and pull in content.
RSS Feed Source#
The RSS Feed source monitors any RSS or Atom feed for new content.
Configuration#
| Field | Description | Required |
|---|---|---|
| Feed URL | The RSS/Atom feed URL | Yes |
| Polling Interval | How often to check (seconds) | No |
| Max Items | Maximum items per poll | No |
Example#
feed_url: "https://example.com/feed.rss"
polling_interval: 300
max_items: 50Reddit Source#
The Reddit source monitors subreddits for new posts.
Configuration#
| Field | Description | Required |
|---|---|---|
| Subreddit | Subreddit name (without r/) | Yes |
| Sort | hot, new, top, rising | No |
| Time Filter | hour, day, week, month, year, all | No |
| Limit | Maximum posts per poll | No |
Example#
subreddit: "netsec"
sort: "new"
time_filter: "day"
limit: 25Telegram Channel Source#
The Telegram source monitors public Telegram channels.
Configuration#
| Field | Description | Required |
|---|---|---|
| Channel | Channel username or ID | Yes |
| Collection Mode | web (scraping) or agent (API) | Yes |
| Agent | Required for agent mode | Conditional |
Collection Modes#
- Web Mode: Scrapes public channel content
- Agent Mode: Uses Telegram API for private channels
Note: Agent mode requires a configured Telegram avatar via the Avatar Selector.
LinkedIn Source#
The LinkedIn source monitors your LinkedIn feed for new posts using browser-based data capture.
Important: This source requires a BYOD Agent with an active LinkedIn avatar. See Configuration Blocks to set up the Avatar Selector.
How It Works#
The agent opens a browser session authenticated with your LinkedIn account, navigates to your feed, and intercepts LinkedIn API responses via XHR capture. Posts are extracted from network traffic — no DOM scraping involved.
Configuration#
| Field | Description | Required | Default |
|---|---|---|---|
| Avatar | Connected Avatar Selector with LinkedIn avatar | Yes | — |
| Monitor Type | Currently only "Timeline" | Yes | Timeline |
| Capture Wait (seconds) | Time to wait for responses (includes scrolling) | No | 60 |
The capture wait value can be between 10 and 120 seconds. Longer waits collect more posts per cycle but increase execution time.
Data Collected#
| Field | Description |
|---|---|
| Content | Post text |
| Author | Author name and profile |
| Timestamp | Publication date |
| Media | Images, videos, shared articles |
| Metrics | Likes, comments, reposts |
Requirements#
- A deployed BYOD Agent with browser support
- An active LinkedIn avatar (authenticated session)
- An Avatar Selector node connected to this source
X (Twitter) Source#
The X (Twitter) source monitors tweets using browser-based data capture via your authenticated account.
Important: This source requires a BYOD Agent with an active X/Twitter avatar. See Configuration Blocks to set up the Avatar Selector.
How It Works#
The agent opens a browser session authenticated with your X account and intercepts GraphQL API responses via XHR capture.
Monitor Types#
| Type | Description | Target Required |
|---|---|---|
| Home Timeline | Your personalized feed | No |
| User Tweets | A specific user's tweets | Yes (username) |
| Hashtag | Search by hashtag | Yes (hashtag) |
Configuration#
| Field | Description | Required | Default |
|---|---|---|---|
| Avatar | Connected Avatar Selector with X avatar | Yes | — |
| Monitor Type | timeline, user_tweets, or hashtag | Yes | timeline |
| Target | Username (for User Tweets) or hashtag | Conditional | — |
| Capture Wait (seconds) | Time to wait for responses | No | 60 |
Target normalization: Leading @ is stripped from usernames and # from hashtags automatically. For example, @elonmusk becomes elonmusk.
The capture wait value can be between 5 and 120 seconds.
Data Collected#
| Field | Description |
|---|---|
| Content | Full tweet text |
| Author | Username and display name |
| Timestamp | Publication date |
| Media | Photos, videos, GIFs |
| Metrics | Likes, retweets, replies, bookmarks |
Requirements#
- A deployed BYOD Agent with browser support
- An active X/Twitter avatar (authenticated session)
- An Avatar Selector node connected to this source
Best Practices#
- Set reasonable polling intervals to avoid rate limits
- Use transforms to filter unwanted content early
- Monitor source health from the dashboard
- For avatar-based sources (LinkedIn, X, Telegram agent mode), use conservative collection frequencies to avoid account flagging
Next Steps#
- Transform Blocks
- Output Blocks
- Configuration Blocks — Set up the Avatar Selector for agent-based sources