Cookbook
Three end-to-end SociaHive recipes — auto-reply to Instagram comments, schedule a week of posts from a CSV, and a daily performance recap from Claude.
Three task-oriented recipes you can copy and run today — no SociaHive UI required. Each one is a real automation built through the same MCP tool surface an AI assistant or a script calls: auto-reply to Instagram comments with a DM, bulk-schedule a week of posts from a CSV via the REST API or CLI, and pull a daily performance recap into your AI assistant's chat. Pick the one that matches your workflow below.
1. Auto-reply to comments
AI user · 2 min · pure prompt. DM anyone who comments “price” on your Instagram posts.
2. Schedule a week from CSV
Developer · 5 min · Python + Node. Bulk-schedule posts across platforms from a spreadsheet.
3. Daily performance recap
Power user · 2 min · pure prompt. One-screen morning brief — what to fix, what to ship, what to watch.
Auto-reply to Instagram comments mentioning "price"
Persona: AI user (Claude.ai, Claude Desktop, Cursor) Time: 2 minutes Code: none — pure prompt via MCP
What you'll build: a SociaHive automation flow that DMs anyone who comments "price", "cost", or "how much" on your Instagram posts. You do it by talking to your AI assistant — no SociaHive UI clicking.
Prerequisites: an MCP client connected to SociaHive — see the MCP setup guide.
The prompt:
Using SociaHive, build me an Instagram comment auto-reply flow:
- Trigger on comments containing "price", "cost", or "how much"
- Reply publicly with "DMing you now! 📩"
- Send the commenter a DM with our pricing link: https://example.com/pricing
- Activate the flow when done
Use my first Instagram account. Show me the final flow before activating.
What the AI does under the hood:
Variations:
| Tweak | Add to your prompt |
|---|---|
| Multiple keyword branches | "If they say 'price' send pricing; if they say 'demo' send a Calendly link" |
| AI-personalized replies | "Reply with an AI-generated message that matches my brand voice — use my knowledge base" |
| Tag the contact | "...and tag the contact with 'price-curious'" |
| Restrict to one post | "Only on Instagram post 18234567890123456" |
Cost: 0 AI credits — generate_flow is creation AI and is free on every
plan. Future auto-replies are also free (template messages cost nothing;
AI-personalized replies cost 5 credits each).
Schedule a week of posts from a CSV
Persona: Developer Time: 5 minutes Code: Python + Node
Prerequisites: a SociaHive API key (see the developer quickstart) and either the Python or Node SDK installed.
CSV format:
CLI one-shot (no scripting needed):
cURL — single call:
Error tips:
413on/posts/bulk— batch cap is 100 rows; chunk your CSV.400 platform_user_id required— account-id lookup matched the wrong account; passplatform_user_idexplicitly.429— default 1000 req/hr per key; cache account IDs and use the bulk endpoint.
Verify: sociahive posts list --status scheduled --limit 20.
Cost: $0 in AI credits.
Daily performance recap with Claude
Persona: Power user / agency operator Time: 2 minutes Code: none — pure prompt via MCP
What you'll get: a one-screen morning brief — which flows underperformed, which posts overperformed, what's queued for today, and where attention is needed. No clicks, no SQL, no dashboard hunting.
Prerequisites: an MCP client connected to SociaHive — see the MCP setup guide.
The prompt:
Give me a brief on yesterday's SociaHive performance. Steps:
- List my flows with stats for the last 24 hours.
- Pull analytics overview for the same window across all platforms.
- List anything scheduled to publish today.
- Output a 6-line summary:
- Top performing flow (by completions) and why
- Worst performing flow (by error rate) and what to investigate
- Top post (by engagement) and what it had in common
- Total reach / impressions across platforms vs the previous day
- Anything queued for today I should review before it ships
- One concrete action you'd recommend
Be concise — under 200 words total. Do not modify anything.
What the AI does under the hood:
All three are read-only tools — no risk of accidental changes, no confirmation prompts.
Variations:
| Tweak | Add to your prompt |
|---|---|
| Weekly instead of daily | "...for the last 7 days instead of 24 hours" |
| Per-platform | "Split the summary per platform — Instagram / Facebook / LinkedIn" |
| Cron-style | Put it in a 9am calendar invite that says "ask Claude" — same prompt |
| Slack-able | "Format the summary as a Slack message with emoji headings" |
Cost:
- 0 SociaHive AI credits — all three tools are read-only metrics endpoints, not metered.
- Whatever your AI assistant charges for its own tokens (usually pennies per run with Claude Haiku or GPT-4o-mini).
Why this beats the dashboard:
The dashboard shows you data. The AI tells you what to do about it — which is what you actually wanted when you opened the dashboard at 9am.
Common questions
Do I need to write code for any of these? Recipes #1 and #3 are pure prompts — you type a sentence to your AI assistant and it calls the MCP tools for you. Recipe #2 (CSV import) has a Python and Node example, but the CLI one-shot and cURL examples in that section work without writing any code at all.
Can I run these with ChatGPT instead of Claude? Yes. Every recipe here uses SociaHive's public MCP server, which any MCP-compatible agent can call — Claude Desktop, Claude Code, ChatGPT Connectors, or Cursor. See the MCP setup guide for per-client connection steps.
What happens if a step fails partway through?
Reads (list_accounts, get_flow, list_flows_with_stats) are always
safe to retry. Writes that are irreversible — publishing a post right now,
deleting a flow — return a short-lived confirmation token on the first
call and only run on a second, explicit confirm; nothing destructive fires
on a single call. For the CSV recipe specifically, see the error tips
above for the common 413 and 429 failure modes and how to recover.
How much do these recipes cost? Recipes #1 and #3 are $0 in AI credits — flow generation and read-only analytics tools are free creation AI, not metered. Recipe #2 doesn't call AI at all; it's direct REST/CLI calls, so it costs nothing beyond your own AI assistant's token usage (if you're driving the CLI from one).
What to read next
- Flow patterns — the seven shapes most SociaHive flows take, so you can describe what you want to build.
- Developer quickstart — REST, SDKs, and CLI reference if you want to wire SociaHive into a larger application.
- MCP setup guide — the AI-assistant integration that unlocks recipe #1 and #3.