- Sales
- v1.0.0
- outreach
LinkedIn limits and warm-up
Use this skill when planning LinkedIn campaign volume, avoiding account restrictions or bans, warming up a new or dormant LinkedIn account, setting safe daily limits for connection requests, DMs, and InMails, or recovering an account from restriction.
SKILL.md
LinkedIn Limits & Warm-Up Protocol
LinkedIn Limits (2024-2026)
Monthly Limits
- 400 connection requests/month (non-premium)
- 800 Open InMails/month (premium members)
- ~120 interactions/day total (stay well below)
Recommended Daily Limits
- 15-20 Direct Messages/day
- 30-40 Open InMails/day
- 10-15 connection requests/day
- 40 "other interactions"/day
What Counts as Interactions
- DMs, connection requests, InMails
- Profile views
- Post likes/comments
- Page likes
- Endorsements
- Joining events/groups
LinkedIn Warm-Up Protocol
When Needed
- Inactive accounts
- New accounts
- Accounts returning from restriction
Process
Days 1-10:
- 60 interactions/day maximum
- Only manual activity (no automation)
- Mix of views, likes, comments
- Focus on genuine engagement
Days 11-20:
- Gradually increase to 80/day
- Start light connection requests (5-10/day)
- Continue manual engagement
Days 21+:
- Gradual increase to full limits
- Introduce automation carefully
- Monitor for warnings
Red Flags to Avoid
- Sudden activity spikes - Gradual increase only
- Same message to everyone - Vary your copy
- Connecting outside work hours - Stay within 9 AM - 6 PM
- Weekend activity - Weekdays only
- Automation too early - Manual first 2-3 weeks
Account Health Indicators
| Indicator | Healthy | Warning | Danger |
|---|---|---|---|
| Connection acceptance | >30% | 15-30% | <15% |
| Message response | >10% | 5-10% | <5% |
| Profile views | Stable | Declining | Blocked |
| Pending connections | <500 | 500-700 | >700 |
Recovery from Restriction
- Stop all automation immediately
- Manual activity only for 2 weeks
- Respond to existing conversations
- Post valuable content
- Engage with others' content
- Slowly reintroduce outreach
Combines with
| Skill | Why |
|---|---|
linkedin-campaign-complete |
Execute campaigns within limits |
linkedin-success-factors |
Apply success rules while respecting limits |
cold-email-4-sequence |
Coordinate LinkedIn + email to reduce LinkedIn load |
Example prompts
Create a 3-week warm-up schedule for my dormant LinkedIn account.
How many connection requests can I safely send per day with 200 pending?
My acceptance rate dropped to 20% - what should I change?
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
Files
1 file ship with this skill. They are installed beside the SKILL.md.
NOTICE1.4 KB
LinkedIn limits and warm-up
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/alex-vacca/linkedin-limits-warmup
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Alex Vacca (https://linkedin.com/in/alex-vacca).
The skill is shared under the MIT License below; this notice must stay with any copy.
MIT License
Copyright (c) 2026 Swan
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.