Local Files Social Media Workflow
This is the core sfeed workflow: keep your posts, media, prompts, and rules on your own machine, let your agent read those files, and use sfeed as the real posting and scheduling layer.
One simple folder
social/
rules.md
queue/
2026-04-14-facebook-update.md
2026-04-15-instagram-launch.md
media/
launch-card.jpg
teaser.mp4
archive/Who does what
- Your files hold the drafts, media paths, and scheduling intent
- Your agent reads those files, follows your rules, drafts the post, and asks for approval
- sfeed handles auth, uploads, posting, scheduling, previews, and the hosted queue
- Facebook and Instagram are the final publishing destinations
Example agent prompt
Read ./social/rules.md and the next file in ./social/queue.
Summarize the draft and tell me which page and platform you plan to use.
If I approve it, use sfeed to post or schedule it with the referenced media file.Why this setup works
You do not have to move your content into a hosted editor before posting. The source of truth stays local, which is easier to version, search, script, and review. sfeed stays focused on the part that actually needs API access.