Connect Eden to Zapier

This is the automation route, not the AI-assistant connection, which signs in through a browser. Zapier runs in the cloud, so it authenticates with a personal access token instead. Give the token read + write access so a Zap can schedule and save on your behalf — a read-only token can only read your workspace.

What you'll need

• An Eden account with scheduling set up (connect your social accounts first).
• A Zapier account with MCP Client available (currently a beta feature).

Step 1 — Generate a personal access token in Eden

1. 01

   Open Settings → Integrations → API access

   In Eden, go to Settings → Integrations and find the API access card.

2. 02

   Generate a Read & write token

   Name it zapier, keep the scope on Read & write (required for scheduling — a read-only token can only read your workspace), and click Generate token.

3. 03

   Copy it now

   Copy the eden_pat_… value immediately — it's shown only once. Eden stores only a hash and can't show it again.

Step 2 — Add Eden as an MCP Client connection in Zapier

1. 01

   Add the MCP Client by Zapier app

   In your Zap, add an action step and choose MCP Client by Zapier, then connect a new remote MCP server.

2. 02

   Enter Eden's server URL and transport

   Set the server URL to:

   https://mcp.eden.so/mcp
   

   Select the HTTP streamable transport (SSE also works), and when asked for a bearer token, paste your eden_pat_… value.

3. 03

   Pick the Eden tool to run

   Zapier loads Eden's tools. Choose one as the action — eden_list_schedules to read your accounts and free slots, or eden_schedule_post / eden_create_scheduling_draft to write.

Step 3 — Build the Zap

1. 01

   Choose your trigger

   Use any Zapier trigger that fits your content source — a Notion database item, a Google Sheets row, a form submission, or a schedule.

2. 02

   Map the fields into the Eden action

   Map your trigger's content into the eden_schedule_post action. A minimal call:

   {
     "text": "Your post text, line breaks preserved",
     "platforms": ["twitter", "linkedin"],
     "scheduledAtIso": "2026-06-25T14:00:00Z"
   }
   

   Leave the time out to use the next free queue slot, or use eden_create_scheduling_draft to land drafts for review rather than publishing automatically.

What Eden can do through the connection

A read + write token isn't limited to scheduling. Eden's tools also let a Zap create notes and append to or rewrite them; create, rename, and trash boards; save links and indexed social posts onto a board; and edit, reschedule, or add a first comment to a queued post — plus all the read tools. See the full list in Connect Eden to n8n. (No folder creation, hard delete, or creator/list mutation.)

A few things to know

• Time must be a timestamp. Use epoch milliseconds (scheduledFor) or an ISO string (scheduledAtIso), not natural language. Format the date in an earlier Zap step if needed.
• Text-only posts work for X, Threads, LinkedIn, and Substack notes. Instagram and TikTok need hosted media — supply a publicly reachable image/video URL.
• Read-only tokens can't schedule. A permission error from eden_schedule_post means the token is read-only — generate a Read & write token and reconnect.

Managing or revoking the token

In Settings → Integrations → API access, each token shows its name, scope, and last-used time, and you can Revoke the Zapier one. Revoking is immediate. Generate a new token to reconnect.

Where to go next

• Want code-style branching and loops? See connect Eden to n8n.
• Prefer Make's visual scenarios? See connect Eden to Make.
• Learn how Eden queues and publishes: scheduling and publishing.