Guides

How to Connect LinkedIn to n8n

Short answer: Use n8n’s MCP Client Tool node with your Cesar connector URL. No custom LinkedIn node.

What you need

  • n8n, cloud or self-hosted, with the MCP Client Tool node.
  • A Cesar Pro or Business plan and the connector URL.
  • Cesar open in a browser with the extension connected while the workflow runs.

Before you add n8n

  1. Cesar is on the Pro or Business plan. In the app, open Integrations and enable LinkedIn MCP.
  2. Copy the connector URL. It already contains the token. Rotating the token in Integrations makes the previous URL stop working.
  3. Keep Cesar open in one browser tab with the Cesar extension installed and LinkedIn signed in. Green status means the bridge is up.

Step by step

  1. 1. Copy the connector URL

    In Cesar, Integrations → LinkedIn MCP → copy the full URL, including ?token=.

    https://mcp.cesar.chat/?token=<secret>
  2. 2. Add the MCP Client Tool

    In the workflow, add the MCP Client Tool node. Set the transport to Streamable HTTP and paste the connector URL as the endpoint. You do not add a Bearer header. The token is already on the URL.

  3. 3. Call a read tool first

    Attach the node to an AI Agent, or run get_connection_status once on its own. If that returns disconnected, the workflow ran while Cesar or the extension was closed.

  4. 4. Keep scheduled runs small

    A schedule can call tools over and over. Cesar paces LinkedIn calls one at a time and cannot send, but a tight loop still hammers the extension. Read and draft. Do not poll the inbox every minute.

Prompts to try first

  • Call get_connection_status, then list_inbox for chats awaiting a reply.
  • For each of those chats, save a draft follow-up with set_chat_draft. Do not send.
  • Apply the label Needs reply with set_chat_label.

Sending is not a tool. Replies land as drafts in Cesar. You send them yourself. The full list is on the LinkedIn MCP server page.

If it does not work

The node cannot see tools

The endpoint must be the full connector URL. A URL without ?token= is rejected.

It works once, then disconnects

The browser running Cesar went to sleep, or the extension disconnected. The workflow needs that browser session at the moment it calls LinkedIn.

Can this put my LinkedIn account at risk?

The agent cannot send a message. LinkedIn calls run one at a time, through the Cesar extension in your browser, not from a copy of the inbox on the server. Cesar does not run outreach sequences. Revoke the connector in Integrations and the URL stops working. Details are in Guardrails built in.

Other AI tools