Auto-publishing posts from Notion to Telegram, VK and Max

Notion content calendar → automatic publishing to TG/VK/Max.

How to set up

Prepare a Notion content database

Create a Database in Notion with fields: Title (post heading), Content (text), Media URL (image links), Status (Draft / Ready / Published), Schedule Date. This becomes your content calendar.

Create a webhook in Crosslybot

In Crosslybot open Channels → Webhook → Create → Inbound, get the Bearer token. Attach the webhook to a project with TG, VK, Max targets.

Set up automation via Notion API + n8n/Make

Use Notion API to read records with Status=Ready. Via n8n / Make.com / Zapier configure a trigger: every 15 minutes read Notion DB → find Ready records → POST to Crosslybot webhook → update status to Published.

Alternative: Notion Webhook + AI

Notion supports webhooks for database changes. When a user changes Status to Ready — Notion sends a webhook to an intermediate service (e.g. Cloudflare Worker), which transforms data and forwards to Crosslybot.

Test via sandbox

Before launching full automation, validate your payload format via POST /v1/sandbox/test. Sandbox checks JSON and media URLs without real publishing.

Features

Notion as content calendar

Notion is ideal for content planning: pages for drafts, tables for scheduling, tags, filters, views. Together with Crosslybot — full chain from idea to publication.

Team collaboration

In Notion, editors write, marketers approve, designers add visuals. When status becomes Ready — Crosslybot picks up and publishes. No manual export.

Publication scheduling

Specify Schedule Date in Notion → automation publishes at the right time via Crosslybot. Time zones, deferred target pause, publication delay — all supported.

AI processing on the fly

Crosslybot runs text through AI before publishing: error correction, translation (for English-language targets), style adaptation. The Notion draft doesn't have to be polished by hand.

FAQ

Can I avoid n8n / Make.com?

Yes — but it requires custom code. For example, a Cloudflare Worker that reads Notion API every N minutes and forwards ready posts to Crosslybot. Off-the-shelf automation (n8n, Make, Zapier) is simpler and gives you a visual workflow diagram.

How to handle media from Notion?

Notion stores files on its CDN, but the URLs are temporary (expire after 1 hour). Best approach: upload images to permanent CDN (S3, Cloudflare R2, ImgBB), and store only URLs in Notion. Then passing them to Crosslybot is trivial.

Can multiple people publish via the webhook simultaneously?

Yes, one webhook accepts requests from different sources. Crosslybot processes them through sequential queue in arrival order — no conflicts.

What if a Notion page has complex formatting (tables, embeds)?

Crosslybot accepts text + entities (bold, italic, links, quotes, spoilers). Complex blocks (tables, embeds, nested databases) lose structure when serialized to plain text. For richly-structured content, consider making a separate viewer page.

Can I publish drafts only after approval?

Yes — that's the advantage of the Notion schema. The Status field (Draft / Pending / Ready / Published) is your approval gate. Automation only publishes records with Status=Ready.

Notion is the standard for content planning in teams: writers, marketers, SMM specialists. Everyone knows Notion databases work great as editorial calendars. The problem — how does Notion data turn into actual posts on TG, VK, Max? Usual path: text export, copy-paste, manual media upload, format checking. Slow and error-prone.

Crosslybot webhook automates this. A record in Notion → Ready → automation (n8n/Make.com or custom code) → POST to Crosslybot → post appears in all social networks. One path, no manual steps between Notion and channels.

Typical chain

Notion DB ──(API poll every 15 min)──► n8n / Make ──(HTTP POST)──► Crosslybot webhook
                                                                          │
                                       ┌──────────────────────────────────┘
                                       ▼
                              Telegram + VK + Max + ...

After publishing in Crosslybot, automation can call Notion API to set Status=Published — the user sees in the content calendar that the post went out.

What to store in Notion

Minimal content database schema:

Title (post name)
Body (rich text — content with formatting)
Media (file array or URLs)
Status (Draft / Pending / Ready / Published)
Schedule Date (when to publish)
Targets (multi-select: TG, VK, Max)
Author
Tags

Crosslybot accepts text, entities, media[], buttons[]. Mapping from Notion to Crosslybot payload is the automation’s job (n8n node or code).

Notion + Crosslybot benefits

Content created in a comfortable tool (Notion as WYSIWYG editor)
Team sees statuses in one place (Draft / Ready / Published)
Schedule managed via Schedule Date field
Crosslybot AI improves text before publishing (if enabled)
One post — all platforms (Telegram, VK, Max), no need to duplicate in Notion

Getting started

Sign up for Crosslybot, activate Pro+
Create a webhook endpoint
Create a Notion database with minimal schema (see above)
Get a Notion API integration token
Configure n8n / Make.com workflow: Notion API trigger → HTTP Request → Crosslybot webhook
Test via sandbox