Post to Social Media from n8n

Schedule, check, and verify social posts from an n8n workflow with the LazyRelay community node, or through LazyRelay's MCP server if you prefer.

Option 1: the LazyRelay community node (recommended)

LazyRelay has its own n8n community node, n8n-nodes-lazyrelay (MIT licensed, on npm). It adds a LazyRelay node and a LazyRelay Trigger node, so you do not have to build HTTP requests by hand.

1. In your LazyRelay dashboard, go to API Keys and create a key. Copy it now, it's only shown once.
2. In n8n, open Settings → Community Nodes → Install, enter n8n-nodes-lazyrelay, accept the community node notice and install. This is for self-hosted n8n for now.
3. Create a LazyRelay API credential and paste in your API key. Leave the Base URL at its default.
4. Add the LazyRelay node to a workflow and pick an operation.

The node can schedule a post, publish now, save and schedule drafts, list, update, delete and approve posts, get a post's public proof link, upload media, look up what a platform accepts, find the next free posting time, read an analytics summary, and create, list and revoke client review links.

The LazyRelay Trigger node starts a workflow when a post is confirmed live (post.verified), fails (post.failed), is sent but not confirmed (post.unconfirmed), or an account needs reconnecting (channel.needs_reconnect). A person creates the webhook endpoint in LazyRelay under Settings → Webhooks using the trigger's URL, then pastes the signing secret into the trigger. The trigger checks each delivery's signature.

Status: the node is unit tested and was run end to end in a real self-hosted n8n (version 2.41.4) against the live LazyRelay API: listing accounts, reading platform rules, listing posts and uploading a file all worked. The trigger node (the webhook side) has been tested with mocks only. If something behaves differently from this page, tell us.

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.

Option 2: MCP Client node (fallback)

If you would rather use n8n's MCP Client node, or you cannot install community nodes, you can connect to LazyRelay's MCP server instead.

1. In your LazyRelay dashboard, go to API Keys (top nav) and create a new key — available on every plan, including Free. 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, so check n8n's own docs for "MCP Client" if the fields above don't match what you see. All 27 tools are available over MCP. Full tool reference (every tool, with what it does) at lazyrelay.com/docs. Building something more custom? See LazyRelay for developers for the REST API and OpenAPI description.