Working with Sources
A Source is any raw material you have expertise locked inside — a podcast episode, a talk, a voice memo, or an artifact from your professional work. Paste a URL or upload a document, and Post Assembly extracts the Ideas worth developing. You don't touch a transcript.
Podcasts & Audio
Paste a podcast RSS feed URL, a direct episode link, or record a voice memo. Post Assembly fetches the audio and transcribes it automatically.
A one-hour episode typically yields 8-15 Ideas — moments of conviction, concrete examples, counterintuitive observations, and clear frameworks. Post Assembly surfaces these; you decide which ones to develop.
- No transcript needed — Post Assembly creates it from audio
- Works with any public podcast URL
- Handles published audio or informal thoughts
YouTube and Video
Paste a YouTube URL. Post Assembly transcribes the video and extracts Ideas from the spoken content.
Conference talks, panel discussions, and recorded interviews are all strong Sources. The transcript stays linked to the Ideas, so you can verify context before publishing.
- Transcription is automatic — no third-party tool required
- Works with any public YouTube video
- Useful for formal or informal video recordings
Web Articles
Paste any public article URL. Post Assembly ingests the text and identifies Ideas worth developing into posts.
Your published writing, newsletters, and long-form pieces on external platforms are all valid Sources. Pieces you've already written elsewhere often contain strong Ideas that never reached your LinkedIn audience.
- No copy-paste required — Post Assembly fetches the content
- Works with most public article URLs
- Good for repurposing your own published writing
What extraction looks like
From a podcast transcript
...and I think the thing that really matters here, and I've seen this over and over again, is that — you know, it's not the abstract principle that people remember, it's the specific example from experience. Like when we actually tried that approach and it didn't work, that's the concrete thing...
To a LinkedIn post
What I've seen over and over again is the things that really matters are the examples. It's not the abstract principle that people remember. It's the specific examples from experience. People remember what you tried — and what happened when it didn't work. That specificity is what makes a post worth sharing.
Any document
Upload any text-based document — meeting notes, a voice memo transcript, document excerpts, email drafts. Post Assembly processes it the same way as any other Source.
This is the most flexible format. If you've jotted down a framework after a client call, or have rough notes from a workshop you ran, raw text gets it into the system without any formatting required.
- No URL needed — just upload the document
- Works well for informal or unstructured material
- Good for capturing ideas that never had a formal home
What Post Assembly does vs. what you do
Post Assembly handles the mechanical work. Fetching audio, transcribing it, reading through the text, finding the moments worth developing — all of this happens automatically when you add a Source.
You handle the editorial judgment. Which Ideas are worth developing? Which ones reflect what you actually believe, not just what sounded good in the moment? Which are specific enough to stand as a post? Post Assembly surfaces the candidates; you decide what moves forward.
This division matters. Transcription and extraction are tasks a system can do reliably. Deciding what represents your point of view is not. Post Assembly automates the first part so you can focus on the second.
Ready to add your first Source?
See how the full workflow connects Sources to Ideas to published posts.