Read the source record
Kollab reads the source URL, transcript, audience, platform list, and current status from your Notion / Buildin content database.
Turn one YouTube video, blog post, podcast, newsletter, or meeting transcript into a reviewed multi-channel content pack stored back in your database.
Repurposing breaks down when the original idea, transcript, platform rules, reviewer notes, and publish status live in separate places. Kollab treats your Notion / Buildin database as the operating system: each source piece becomes a record with channel assets, review status, and learning notes.
Use it after publishing a long-form piece. Kollab extracts the core idea, creates platform-native drafts, flags claims that need checking, writes every asset back to the database, and leaves the final publish decision to you.

Read through the workflow once, then swap in your own roles, sources, and outputs.
Kollab reads the source URL, transcript, audience, platform list, and current status from your Notion / Buildin content database.
The agent pulls out the core promise, proof points, claims to verify, and the parts worth adapting for each channel.
Each platform gets its own draft page with format, hook, CTA, visual notes, and review checklist instead of one generic summary.
Kollab updates database status, reviewer, publish date, linked draft pages, and priority so the creator still controls publishing.
Kollab keeps the source idea, channel drafts, review state, and learning loop in one database.
| Manual repurposing | With Kollab | |
|---|---|---|
| Source context | Paste transcripts into separate chats and lose the original angle after the first rewrite. | The source record, transcript, core idea, audience, and platform list stay connected. |
| Platform fit | Shorten the same text for every channel, making each post feel generic. | Each draft is rewritten for platform behavior, format, length, hook, and CTA. |
| Review | Track feedback in comments, DMs, or memory. | Every asset has status, reviewer, checklist, linked draft page, and publish date. |
| Learning loop | Performance notes rarely return to the next source piece. | Performance notes sit beside the asset and inform future repurposing runs. |
| Total time | Scattered drafts and weak reuse | One reviewed multi-channel pipeline |
Each run should leave usable drafts and database state, not just a paragraph of advice.
Database
Drafts
Review
Follow the related capability pages to see which product layers and tools make this use case repeatable for a team.
Turn one YouTube video, blog post, podcast, newsletter, or meeting transcript into a reviewed multi-channel content pack stored back in your database.
Copy the setup prompt into Kollab, replace the placeholders with your team context, then run it as a reviewable task in your workspace.
A Notion content repurposing database with linked draft pages for X, LinkedIn, newsletter, Shorts, TikTok, and Instagram, plus status, reviewer, publish dates, privacy checks, and review notes.
No. The workflow is designed to produce reviewable drafts, briefs, artifacts, or database updates first, so your team can approve the result before anything is published or changed.
Keep the source, drafts, review state, and publishing plan inside your Notion database.
Run