Turn Your Instagram Saves Into a Self-Running Content Engine with Claude Code

The problem with saving posts for later

Every creator has the same habit: see something interesting, tap save, move on. The save pile grows. The ideas never materialize.

The bottleneck isn't inspiration — it's the gap between saving content and doing something with it. This guide closes that gap with a pipeline that runs automatically, processes your saves on a schedule, and hands you finished content ideas every week.

Hypd recommends building systems that do the repeat work so you can focus on the decisions that matter. This is one of them.

What the pipeline does

Three components work together: a Python sync daemon that pulls your Instagram saved posts into a Notion database, a launchd scheduler that runs the daemon automatically on macOS, and a Claude Code slash command that reads those saves and generates platform-specific content ideas in your voice.

Claude Code writes the sync script for you — no Python experience required. You configure it once, and the pipeline runs in the background from that point forward.

• Instagram saves → Notion database (synced automatically via launchd)
• Notion database → content ideas (generated weekly via Claude Code slash command)
• Each idea includes platform breakdown and brand voice alignment
• Handles duplicate prevention via a local state file

One-time setup: what to build

The setup has eight steps, but most of the heavy lifting is done by Claude Code. Your job is to wire up the credentials and run the commands.

• Create two Notion databases: one for Instagram Saves (Status, URL, caption, author, date) and one for Content Ideas (linked saves, pillar, platform, idea text)
• Connect a Notion integration to both databases and copy the integration token
• Capture your Instagram session cookies from Chrome DevTools → Application → Cookies on instagram.com (sessionid, csrftoken, ds_user_id)
• Ask Claude Code to generate sync.py, config.example.json, requirements.txt, and .gitignore for an Instagram-to-Notion sync tool
• Create a Python virtual environment, install dependencies, and fill in config.json with your real credentials
• Run sync.py manually — confirm rows appear in Notion with Status = New
• Install the launchd plist so the sync runs on schedule without manual intervention
• Create a Claude Code slash command at .claude/commands/instagram-sync.md to control the ideation cycle

Claude Code prompt to generate the sync script

Use this prompt inside Claude Code to generate all the files you need for the sync daemon. Paste it into a new Claude Code session inside your project folder.

promptCopy
Build an Instagram saved posts sync daemon for me.

I want a Python script called sync.py that:
1. Reads Instagram session cookies from a config.json file (sessionid, csrftoken, ds_user_id)
2. Fetches my saved posts from the Instagram API
3. Writes each new save to a Notion database (properties: URL, Caption, Author, Saved Date, Status=New)
4. Tracks already-synced posts in a state.json file to prevent duplicates
5. Exits cleanly if no new saves are found

Also generate:
- config.example.json with placeholder values for all credentials
- requirements.txt with all dependencies
- .gitignore that excludes config.json and state.json

Notion database ID and integration token should come from config.json.
Do not hardcode any credentials.

Claude Code slash command for weekly ideation

Once the sync is running, create this slash command file at .claude/commands/instagram-sync.md. Update the database IDs and niche placeholders for your account before using it.

promptCopy
Read all rows in my Instagram Saves Notion database where Status = New.

For each save:
1. Identify which content pillar it maps to based on the caption and URL
   Pillars: [LIST YOUR PILLARS HERE — e.g. productivity, AI tools, business systems]
2. Generate one content idea per platform: Instagram carousel, LinkedIn post, short-form video hook
3. Write the idea in my voice: direct, practical, no fluff, business-owner audience
4. Update the row Status to Processed
5. Create a linked entry in my Content Ideas database with: Pillar, Platform, Idea Text, Source Save

After processing all saves, print a summary: how many processed, ideas by pillar, any saves you skipped and why.

Notion databases:
- Instagram Saves: [YOUR SAVES DATABASE ID]
- Content Ideas: [YOUR IDEAS DATABASE ID]

Weekly workflow and maintenance

Once the setup is complete, the weekly routine takes about five minutes. The sync daemon handles the rest automatically.

• Open Claude Code in your project folder each week
• Run /instagram-sync to trigger the ideation cycle
• Review the ideas generated in your Content Ideas database
• Approve and schedule the ones that fit your content calendar
• If sync stops working: refresh your Instagram cookies from Chrome DevTools and update config.json — session cookies expire periodically
• Back up state.json occasionally — it's the only thing preventing duplicate Notion entries

Expanding to other platforms

The same pattern works beyond Instagram. The sync daemon follows a consistent structure: authenticate via session or API, fetch saved or bookmarked content, write to Notion, track state locally.

The same approach applies to X bookmarks, YouTube watch-later lists, and TikTok saves. Each platform needs its own authentication method, but the Notion write logic and Claude Code slash command stay the same.

Frequently asked questions

• Do I need Python experience to set this up? No. Claude Code generates all the code. Your job is to provide credentials, run the commands it tells you to, and confirm the sync works. The guide is designed for non-developers.
• How often should the sync daemon run? Weekly batching is recommended over daily runs — it reduces cognitive load when reviewing ideas and tends to produce sharper creative output. Adjust the launchd schedule to match your publishing rhythm.
• What happens if my Instagram session expires? The sync will fail silently. Run /instagram-sync refresh session in Claude Code, grab fresh cookies from Chrome DevTools on instagram.com, update config.json, and run sync.py manually to confirm it's working again.