pooriaarab Instagram Saved Organizer
Process Instagram saved posts and collections.
Requirements
- Instagram account.
instaclawCLI — pooriaarab/instaclaw (scaffold; needs implementation). Browser-cookie-based scraper in steipete's*clawstyle. Goal: claw saved posts and collections into structured JSON.- Logged-in Instagram session in a browser (Meta auth shared with Threads).
- Fallback until
instaclawis built: Meta's "Download Your Information" data export, or Playwright on the web app.
Step 1 — Ask the User First
1. Goal — export, restructure collections in-place, or both?
2. Already using Collections? — keep, consolidate, or rebuild?
3. Categorization — by content type (food / travel / fashion / how-to), by source (creator)?
4. After export — unsave, or leave originals?
5. Source — work from "Your Activity → Saved" or from a "Download Your Data" archive?
Steps (TBD)
- Inventory — fetch saved list (URL, post type, creator) via web scrape or downloaded archive.
- Classify — by collection or AI-suggested category.
- Plan — collection restructure + export TSV.
- Approve — batch by collection.
- Apply — Instagram's web app supports moving between collections; bulk operations are tedious — consider per-collection batches.
- Verify — final saves count + collection structure.
Surface-specific notes
- No public API for saved posts. Instagram's "Download Your Data" feature is the most reliable bulk source.
- Anti-scraping is strict; the web app can rate-limit aggressively.
- Reels-vs-Posts have separate saved lists in some accounts.
- High-volume saves (1000+) often indicate "saved-as-bookmark" intent — most users want to convert these into Notion.