# Build a Social Media Agent Without Code (Zapier, Make, n8n)

**TL;DR:** You don’t need MCP or Claude to automate ViralNote. Use the **REST API** with Zapier, Make, or n8n: trigger on RSS, Google Sheets, or form submits → HTTP POST to schedule posts. Add **webhooks** for publish/fail alerts. Graduate to MCP when you want conversational control.

“AI agent” doesn’t always mean an LLM loop. For many creators, a **no-code automation** *is* the agent — it runs the same schedule every week without chat.

## When no-code is the right choice

| Use no-code | Use MCP / LLM agent |
|-------------|---------------------|
| Fixed weekly RSS → social | Variable captions needing judgment |
| Form → schedule post | “Review my calendar and fix gaps” |
| Alert on publish failure | Multi-step research + schedule |
| Team without dev resources | Developer in Cursor daily |

## Prerequisites

1. ViralNote account + [API key](https://dashboard.viralnote.app/developers/auth)
2. Zapier, Make, or n8n account
3. Connected social accounts in ViralNote dashboard

Base URL: `https://dashboard.viralnote.app/api/v1`  
Auth header: `x-api-key: vnd_...` (or `Authorization: Bearer vnd_...`)

## Pattern 1: RSS → scheduled posts (Zapier / Make)

**Trigger:** New item in RSS feed (your blog/podcast)

**Action:** Webhooks by Zapier → POST `/posts`

```json
{
  "caption": "{{title}} — {{link}}",
  "platforms": ["linkedin", "x"],
  "status": "scheduled",
  "scheduledFor": "{{tomorrow 9am ISO}}",
  "is_draft": false
}
```

**Tips:**

- Map `title`/`link` from RSS fields
- Start with one platform; expand after a week of clean runs
- Use `is_draft: true` first if you want manual approval in ViralNote UI

## Pattern 2: Google Sheets → bulk schedule (Make)

**Trigger:** New row in sheet (columns: caption, platforms, datetime, media_url)

**Steps:**

1. HTTP — `POST /media/import` if `media_url` present
2. HTTP — `POST /posts` with `libraryItemId` from step 1
3. Router — on 429, delay and retry

Make handles iteration natively; Zapier may need one zap per row or use Zapier Tables + looping.

## Pattern 3: Publish alerts (n8n + webhooks)

1. Create webhook in ViralNote (dashboard or API) → n8n Webhook URL
2. On `post.failed` → Slack message
3. On `post.published` → append row to Airtable

Full walkthrough: [Webhooks + n8n](/blog/webhooks-n8n-agent-triggers-social-media).

## Pattern 4: “Human in the loop” without an LLM

1. Typeform/Tally submission → Zapier
2. Create **draft** post in ViralNote (`is_draft: true`)
3. Slack notification: “Approve in dashboard”
4. You click publish in UI

No model risk; still saves copy-paste time.

## API endpoints you’ll use most

| Endpoint | Purpose |
|----------|---------|
| `GET /posts` | List queue |
| `POST /posts` | Create scheduled/draft |
| `POST /media/import` | Pull image/video from URL |
| `GET /social-accounts` | Verify connected platforms |
| `POST /webhooks` | Event-driven flows |

OpenAPI: [viralnote.app/api/v1/openapi](https://www.viralnote.app/api/v1/openapi)

## When to add an LLM layer

Add MCP or a skill when:

- Captions need per-platform tone every week
- You want natural language (“schedule like last month but skip Fridays”)
- You’re already in Cursor/Claude daily

Bridge guide: [MCP vs skill vs API](/blog/mcp-vs-skill-vs-api-viralnote-agent).

## Common mistakes

1. **Publishing immediately** — use `scheduled` + future `scheduledFor` until you trust the zap
2. **Wrong platform slugs** — call `GET /social-accounts` once and copy exact platform ids
3. **No error handling** — log `requestId` from error JSON for support
4. **One API key everywhere** — separate keys per Zapier vs personal scripts

## Stack comparison

| Tool | Strength | ViralNote fit |
|------|----------|---------------|
| Zapier | Easiest, fewer steps | RSS, simple POST |
| Make | Visual, multi-step | Sheet bulk, branches |
| n8n | Self-host, webhooks | Event-driven, technical teams |

## Next steps

- [30-minute weekly workflow](/blog/how-to-schedule-a-week-of-posts-in-30-minutes) — clipping + scheduling in ViralNote UI
- [Automate with an AI agent](/blog/automate-week-of-posts-ai-agent-2026) — when you’re ready for MCP
- [Developers docs](https://www.viralnote.app/developers/docs)

Automation is an agent that doesn’t chat. Start no-code; add intelligence when the workflow earns it.

## FAQ

**Can I automate ViralNote without coding?**

Yes. Zapier, Make, and n8n can POST to ViralNote's REST API with your API key — common patterns include RSS to scheduled posts and Google Sheets bulk import.

**Zapier or Make for ViralNote?**

Zapier is fastest for simple RSS → POST flows. Make handles multi-step sheet iteration and branching better. n8n excels at webhooks and self-hosting.

**When should I add an LLM agent on top of Zapier?**

When you need per-platform caption judgment or natural-language calendar changes weekly. Until then, no-code REST automation is simpler and more predictable.


---

Site index for agents: https://www.viralnote.app/llms.txt · Structured view: https://www.viralnote.app/agent.json · API: https://www.viralnote.app/openapi.json · Auth: https://www.viralnote.app/auth.md