linkedin + n8n

esoterikizym

Regular Member
Joined
May 15, 2017
Messages
376
Reaction score
89
has anyone successfully created an n8n workflow for linkedin that would message people and schedule appointments yet?
 
Very possible, are you trying to attempt this for scheduling services for business outreach like b2b service or something along those lines?
 
Engagement. Commenting on monitored profiles when they post
 
has anyone successfully created an n8n workflow for linkedin that would message people and schedule appointments yet?
Yep, I’ve built one. I use n8n’s HTTP Request node against LinkedIn’s API (you need a Sales Navigator token), then parse connections and send personalized messages in a loop. After a reply comes in, I trigger a Google Calendar node to auto-create an event and email both parties. You’ll need to handle rate limits carefully and store your OAuth credentials securely, but once set up it runs reliably.
 
Tried building one with LinkedIn API + Calendly in n8n... hit rate limits fast :confused: Still tweaking it curious if anyone’s got a solid setup running :cool:
 
Tried building one with LinkedIn API + Calendly in n8n... hit rate limits fast :confused: Still tweaking it curious if anyone’s got a solid setup running :cool:
What have you tried to do to mitigate these rate limits just curious. Hope you find something that works for you.

Best,
Bryce
 
Yep, I’ve built one. I use n8n’s HTTP Request node against LinkedIn’s API (you need a Sales Navigator token), then parse connections and send personalized messages in a loop. After a reply comes in, I trigger a Google Calendar node to auto-create an event and email both parties. You’ll need to handle rate limits carefully and store your OAuth credentials securely, but once set up it runs reliably.
Does it auto reply when someone messages back and have a conversation until it books to my calendar?
 
has anyone successfully created an n8n workflow for linkedin that would message people and schedule appointments yet?
Some solid advice in this thread already. The users pointing out that LinkedIn's official API is a dead-end for this kind of task are 100% correct. You have to use a third-party automation tool to interact with the front-end.
The approach of using a tool like **PhantomBuster** and connecting it to n8n via webhooks is the standard, effective way to build this.
The way to think about this strategically is that you're building a two-part system:
1. **The Specialist 'Agent'**: This is your PhantomBuster (or a similar tool). Its *only* job is to be the expert at interacting with LinkedIn's interface. It's your specialized digital worker that handles the risky, front-line task.
2. **The 'Orchestrator'**: This is **n8n**. Its job is to be the brain of the operation. It should never touch LinkedIn directly. It just tells the Specialist Agent *when* to work (e.g., "run this Phantom now"), gives it the data it needs (e.g., "here is the personalized message to send"), and then takes the results back for processing (e.g., "log the successful sends in a Google Sheet").
This model is powerful because it's modular. If your PhantomBuster 'agent' has issues, or if a better LinkedIn tool comes along next month, you can just swap out that one component. Your core business logic inside n8n (the orchestrator) remains safe and unchanged.
And just to echo what others have wisely said: be extremely careful. This is a clear violation of LinkedIn's ToS. Don't run this on an account you can't afford to lose. Warm it up slowly, use high-quality proxies, and keep the volume reasonable.
Good luck with the build.
 
Back
Top