# n8n is workflow automation, not a LinkedIn sequencer
> n8n is an open workflow tool: triggers, nodes, and code when you need it. You can call official APIs you already have. It is not a LinkedIn invite product.
- HTML: https://omentir.com/n8n
- Markdown: https://omentir.com/n8n.md

## What you actually install

[n8n](https://n8n.io) is a workflow automation platform for technical teams. You build graphs: a trigger (webhook, schedule, app event), then nodes that transform data, call APIs, write to a database, or ping Slack. You can write JavaScript or Python in a step when the visual node is not enough. You can self-host (Docker is the common path) or use their hosted product. The source is public. That is the object. It is closer to Zapier or Make in job-to-be-done, with more of an engineering bias: git, environments, code in the graph.

People search 'n8n LinkedIn' because they want a cheap sequencer. n8n will not give you a LinkedIn warmup policy, a native invite inbox, or a campaign UI that understands connection notes versus InMail. It will give you HTTP Request nodes and a community of packages. Those are different gifts.

*n8n is a graph: trigger, transform, write. It is not a LinkedIn campaign UI.*

## Where n8n is the right tool

Ops examples that fit: a form fill hits a webhook, n8n enriches the row, writes the CRM, and opens a Slack message for a human. A won deal in Salesforce provisions a seat in another system. A support ticket gets a lookup in three tools and a drafted reply for review. Security and IT teams use it for the same pattern with different systems. If you can describe the work as 'when X, do Y in Z, then tell a person,' n8n is in the shortlist.

AI steps exist in the product story (calling models, evaluating outputs). Treat those as nodes with failure modes, not as a salesperson. Keep a human on anything that leaves your company as a message to a customer.

## Where LinkedIn enters, and where it should not

You can call official LinkedIn APIs from n8n if you have an app, tokens, and a use case the [developer docs](https://learn.microsoft.com/en-us/linkedin/) allow: ads reporting into a warehouse, Page comment routing, Sign In callbacks. That is integration work. It is allowed to the extent LinkedIn granted the scopes.

Community nodes or DIY cookie flows that log into a member profile and send invites are unofficial automation with the same account risk as any sequencer, plus you are now the vendor. n8n will not save you from a restriction. It will make the restriction more reproducible. Do not run that on a profile you care about unless you are deliberately in the LinkedIn automation business and you understand the terms.

## n8n versus a sequencer versus a workspace

Buy n8n when the bottleneck is glue between systems you already pay for. Buy a LinkedIn sequencer when the bottleneck is paced invites on a list. Buy a LinkedIn workspace when the bottleneck is finding the people and sending from a profile with an inbox. Forcing n8n to be the sequencer usually means a weekend of nodes that recreate 10% of Expandi and 0% of the safety UI. Use n8n to push 'reply received' into the CRM after a real LinkedIn tool did the sending.

## Related

- [Social media marketing](https://omentir.com/social-media-marketing.md)
- [Workflow automation: the ops definition, then sales](https://omentir.com/workflow-automation.md)
- [Digital marketing, with email in its place](https://omentir.com/digital-marketing.md)

## Common questions

**Is n8n free?**

The software can be self-hosted under its license terms, which you should read on n8n's site and GitHub. Hosted n8n is a paid product. Self-hosting still costs your time, servers, and the credentials of every app you connect.

**Can n8n replace Zapier for a non-technical team?**

Sometimes, if someone on the team will own the graphs. n8n rewards people who debug JSON. If nobody will, a simpler hosted connector tool may fail less often, at the cost of flexibility.

[Create an Omentir account](https://omentir.com/signup). Pro is $49/month.