← Documentation: Instagram Reel to Notion Second Brain


Test each integration through a real Telegram message so you can verify the saved page as well as the n8n execution. Use public Reels with clear speech and keep only one workflow active for the bot token.

1. Confirm the basic route

Send /help; it should reply without calling Apify. Then submit a public Reel and follow Telegram, Apify, OpenAI and Notion in the execution.

The Inbox entry should contain Titolo, Tipo, Categoria, Stato, Fonte and Data, plus readable knowledge sections. The Telegram reply should link to that page.

2. Inspect extraction quality

Use a Reel in a different language from your chosen output. IT should produce Italian entries and EN should produce English entries while retaining original technical names.

Test a meaningful caption containing a promotional prompt such as “comment SETUP”. Useful facts should remain and promotional instructions should be excluded. Links must come from the available source text; the workflow does not inspect frames or verify repositories.

Submit the same Reel again only when testing repeat behavior: a second page and additional API usage are expected.

3. Verify failure behavior

Unsupported URLs should be rejected before paid calls. Private or inaccessible content and empty transcripts should stop the AI/Notion route rather than create an empty entry. An Actor still incomplete after the wait should return a timeout status.

For model or parser errors, inspect 15 — Analyze Reel With AI and the raw parser output. For Notion failures, inspect access, schema and Expression-mode fields. For Telegram errors, inspect chat ID and HTML escaping.

Retry and operate

Check execution history and the destination database before retrying a failed delivery; a page may already exist. There is no guaranteed recovery or deduplication after integration failure.

Confirm the allowed user ID, database mappings and provider quotas before regular use. When sharing an export, remove personal user IDs, private database IDs, pinned data, credential metadata and secrets.