Post to Social Media from n8n

Give an n8n workflow the ability to schedule, check, and verify social posts through LazyRelay's MCP server — no custom HTTP nodes to hand-build.

What this unlocks

• An AI Agent node that can schedule a post as part of a larger workflow (e.g. "new blog post published → draft and schedule a promo post").
• A workflow step that checks whether a post from earlier in the automation actually went live before moving on.
• Pulling analytics into a report that gets emailed or posted to Slack on a schedule.

The part most AI-agent schedulers skip

Most integrations stop at the API call — a workflow fires a "create post" request, gets a 200 OK, and moves on. That isn't proof the post is live. Rate limits, silent moderation holds, and platform-side failures can all eat a "successful" request. LazyRelay's list_scheduled_posts tool returns real Proof-of-Publish status, so a workflow can branch on whether a post is actually confirmed live, not just accepted.

Setup

1. In your LazyRelay dashboard, go to API Keys (top nav) and create a new key. Requires a paid plan — Starter and up. Copy it now, it's only shown once.
2. In your n8n workflow, add an MCP Client node (n8n's built-in node for connecting to MCP servers) and point it at LazyRelay's hosted MCP endpoint:

   https://lazyrelaylazyrelay-backend.onrender.com/mcp

   If your n8n MCP node needs a local command instead of a URL, use npx -y @lazyrelay/mcp-server with LAZYRELAY_API_KEY set in its environment.
3. Wire the MCP Client node's tools into an AI Agent node, or call them directly as a workflow step.

n8n's exact MCP node configuration has changed as the feature has matured — check n8n's own docs for "MCP Client" if the fields above don't match what you see. Full tool reference (list_connected_accounts, schedule_post, list_scheduled_posts, delete_scheduled_post, get_analytics_summary, get_mentions) at lazyrelay.com/docs.