Automatically populating a blog from external 1C-Bitrix sources

Auto-Filling a Blog from External Sources in 1C-Bitrix

A corporate blog requires regular publications — both for SEO traffic and to demonstrate expertise. Internal resources for content creation are limited, however. Auto-filling from external sources (industry news, partner articles, professional community publications) allows the section to remain active with minimal editorial involvement.

Differences from RSS News Aggregation

A blog is not a news feed. The key differences in content approach:

• News: timeliness matters more than quality; published quickly, often as a summary + link
• Blog: quality matters more than speed; a unique angle is required; long-form content

For a blog, automatic import produces a draft, not a final piece. The system creates entries with status ACTIVE = N; an editor reviews them and publishes — with minimal edits if any.

Content Sources for a Blog

Professional platforms (Habr, Medium, dev.to) — via RSS API. Habr provides RSS by hub: https://habr.com/ru/rss/hubs/php/articles/.

YouTube channels — via YouTube Data API v3. Retrieve the video transcript via youtube-transcript-api (Python) or third-party services → adapt into article text.

Telegram channels — via MTProto API (Telethon/Pyrogram), or public channels via RSS converters (rsshub.app).

Own article base in multiple languages — if the company has a blog in one language, automatically translate to other languages via DeepL API or GPT.

Content Processing and Adaptation

Aggregated content cannot be published as-is. Minimum processing pipeline:

1. HTML sanitization — HTMLPurifier with an allowed tag set (p, h2-h4, ul, ol, li, strong, em, a, img)
2. Source branding removal — regex replacement of source company mentions
3. Headline adaptation — reformulation via AI or template-based addition of the site's topic
4. Introduction generation — AI generates 1–2 opening paragraphs in the blog's style
5. CTA addition — a block linking to a relevant service or product is automatically appended

Editorial Workflow

The system acts as an editorial assistant, not a replacement:

1. The system creates a draft in the blog info block (ACTIVE = N, ACTIVE_FROM = date+3days)
2. The editor receives a notification about new drafts (daily digest via \Bitrix\Main\Mail\Event)
3. The editor reviews, edits if necessary, and publishes
4. If a draft has not been reviewed after 7 days — a repeat notification is sent

Additionally: AI scoring of each draft on parameters (uniqueness, readability, relevance to the site's topic). The editor sees the score and can filter by it.

Technical Components in 1C-Bitrix

The blog is implemented as a standard info block. Additional properties for auto-filling:

• SOURCE_URL — link to the original
• SOURCE_NAME — source name
• AUTO_DRAFT — flag for automatically created drafts
• CONTENT_SCORE — content quality score (0–100)
• PUBLICATION_DATE_PLANNED — planned publication date

Project Timeline

Total: 7–12 working days depending on the set of sources.