LinkedIn Integrations for n8n and Albato

n8n and Albato both ship a built-in LinkedIn integration, and both of them publish content. The n8n node has a single operation, Create a post, and Albato’s app covers posts, comments and page statistics. To send a connection request or a message from a workflow you need an account-based LinkedIn API, and on both platforms ours comes as a ready-made app.

Below: what each built-in app covers and why sending is missing from both, what an account-based API adds, and the setup on each platform. The sending budget lives on the server that makes the call, checked before anything reaches LinkedIn. On that stack, gtm-api.com runs 20,000+ accounts with under 1% of them ever restricted.

What each platform’s LinkedIn app actually does

Both built-in apps are wrappers around LinkedIn’s official Share and Pages products, so they do what those products do: publish a post, publish to a company page, and read a few page statistics. Search, connections, messages and inbound events are outside both of them. The table puts the two built-in apps in one row, since they cover the same ground (checked against each platform’s own documentation, n8n’s in August 2026 and Albato’s in October), next to the two ready-made gtm-api apps and the plain HTTP route. Both apps were tested action by action and trigger by trigger on live accounts.

Both gtm-api apps search from a LinkedIn search URL, and their three events are a message received, an invitation accepted and an invitation received. Through the API itself the same key also searches Sales Navigator, sends InMail and posts as a person, as a company page or into a group. The built-in apps post as a person or an organization, and Albato’s adds comments, reactions and page statistics.

n8n’s own documentation says the quiet part out loud on the node’s reference page: “If this node doesn’t support the operation you want to do, you can use the HTTP Request node to call the service’s API.” That sentence is the real integration path on every one of these platforms, and the rest of this page is about which API you point it at.

Why the built-in apps cannot send a connection request

The gap is upstream of the platforms. LinkedIn documents an Invitations API and a Messages API, and both sit inside its Compliance program, which LinkedIn lists as closed to new applications. The published scopes grant no sending, and the program’s terms require the member to compose and send each message themselves. A public app on a marketplace cannot ship an action it has no legal path to call.

So a LinkedIn integration built on the official API can only reach the products that are self-serve, and those are Share on LinkedIn and Sign In with LinkedIn. That is exactly the shape of both built-in apps. The full map of what LinkedIn opens, what needs partner approval and what is closed outright is on LinkedIn API: the developer guide, with the application paths on How to get official LinkedIn API access.

Everything else in this article runs on the other model. An account-based API acts through a LinkedIn account you connect yourself, in an isolated cloud browser session with its own proxy, so the actions available are the ones a member has: search, invite, message, enrich, engage.

What an account-based API adds to a workflow

One credential and a normal HTTP step gives a workflow the outreach half of LinkedIn. The calls are typed REST, they return parsed objects, and every outward action passes a server-side budget before it reaches LinkedIn. Nothing about the platform changes: the same node, module or webhook step that talks to any other API talks to this one.

curl -X POST https://app.gtm-api.com/linkedin/v4/api/linkedin-connection-requests/send \
  -H "Authorization: Bearer $GTM_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"linkedin_account_sid": "ln_ac_...", "profile_id": "ACoAA...", "note": "..."}'

Inbound events are the half a scheduler cannot fake. A polling workflow that checks for new replies every five minutes burns capacity on the account and still arrives late. Webhook subscriptions push the event instead, and each subscription names the event types it wants.

• Invitation accepted. linkedin-connection-requests.accepted fires when the person on the other end accepts, which is the trigger most sequences are really waiting for.
• Reply received. linkedin-messages.received covers the inbound message, and linkedin-messages.sent confirms an outbound one landed.
• Limit reached. linkedin-account-smart-limits.limit-reached tells the workflow the account is out of budget for that action, before the next step wastes an attempt.
• Account trouble. linkedin-accounts.login-failed and linkedin-account-block-log.recorded surface a session or an enforcement problem while it is still recoverable.

LinkedIn in n8n

The shortest route is a community node. Several LinkedIn API vendors publish one for their own API, and ours, n8n-nodes-gtm-api, wraps the invitation, message, enrichment and people-search calls and adds a trigger on three LinkedIn events. n8n verified it on 7 October 2026, so it installs from the nodes panel on n8n Cloud as well as self-hosted. Install, credential and operations are covered on n8n LinkedIn node.

For a call the node does not wrap, use the HTTP Request node. The setup is three fields. Create a Header Auth credential with the name Authorization and the value Bearer followed by your token, set the node’s method to POST and the URL to the endpoint you want, and put the request body in as JSON. Because everything is one host and one credential, adding a second action later is a copy of the node with a new path. For the trigger side without the node, an n8n Webhook node gives you a public URL, and that URL goes into a webhook subscription with the event types above.

For an agent workflow, n8n ships an MCP Client Tool node that attaches an external MCP server and hands its tools to the agent, with bearer and OAuth2 credentials supported. The built-in LinkedIn node stays useful for what it does well, publishing posts, and it can sit in the same workflow as any of these on its own credential.

LinkedIn in Albato

Albato’s built-in LinkedIn app, the one Albato makes itself, is a publishing app like n8n’s: seven actions covering posts on a personal page or an organization page, comments, reactions on comments, follower and organization statistics, and a Custom API request scoped to LinkedIn’s official API, and no triggers.

The gtm-api app in Albato adds the outreach half as ready-made steps. It has four actions, Send Connection Request, Send Message, Enrich Person and Search People by URL, and three triggers, Message Received, Connection Request Accepted and Invitation Received. The connection takes an API key, every action starts with a Sender list filled from the LinkedIn accounts you connected, and the triggers register their webhook when an automation starts and remove it when the last one stops. A call the app does not wrap goes through Albato’s HTTP request step with the same key in an Authorization header.

One design rule carries across both platforms: the workflow schedules the sending and the server paces it. A scheduler fires what it is told at the interval it is told, so a 200-row sheet pushed into a send step lands all at once, while a server that checks a per-account budget before each call spreads it out and stops when the budget is spent. Push the whole list, subscribe to the limit event if the workflow needs to know, and read Safe LinkedIn automation and LinkedIn limits for what keeps the account itself healthy.

Frequently Asked Questions

Read next on this topic

Sources & Further Reading

• n8n, LinkedIn node reference (the single Post: Create operation, and the HTTP Request fallback quoted above), read 20 August 2026
• n8n, MCP Client Tool node (bearer and OAuth2 credentials for an external MCP server), read 20 August 2026
• n8n, community node catalog entry for n8n-nodes-gtm-api (both nodes marked verified and published on 7 October 2026), read 7 October 2026
• Albato, LinkedIn integrations (seven actions and no triggers), read 23 October 2026
• gtm-api.com, developer documentation (the endpoint and webhook event names used above)
• Related: LinkedIn API: the developer guide · LinkedIn MCP server · How to get official LinkedIn API access · LinkedIn limits · Safe LinkedIn automation · Automate LinkedIn with n8n · n8n LinkedIn node

Michael SalamatovGTM engineerRuns the gtm-api.com blog. Covers LinkedIn limits, account health and the API side of outbound.in

Last updated: October 2026 · Definitions and benchmarks verified at time of publication