Safest LinkedIn Automation Tools: What Each Vendor Publishes

The safest LinkedIn automation tool for your account is the one whose safety controls you can read, set and check before you connect anything. Ask every vendor to show eight of them in its own documentation: randomized timing, settable caps, working hours, warm-up, a review step, an IP or proxy per account, one session per account and a cloud browser per account.

First the audit: what to ask a vendor, what a real answer looks like on its own pages, and what a missing one costs you. Then the matrix of 43 tools, sorted by how many of the eight controls each one publishes, and one section per control with the vendor’s words behind every cell. The category itself, how it runs, what it costs and where its limits sit, is on the LinkedIn automation hub.

How to audit a vendor’s safety claim

Split the claim in two before you weigh it. An outcome claim, such as “safe”, “zero bans” or a restriction figure, describes what happened to other customers’ accounts, and you can’t check it from outside or line it up against another vendor’s. A control is something the tool does to your account, described in the vendor’s own documentation and visible in the settings once you sign up. Audit the controls. Whether automation is safe at all, and what gets an account restricted in the first place, is covered in the safe LinkedIn automation guide. This page compares vendors.

The questions to send a vendor

Ask for every answer as a link to the vendor’s own help center or docs. A line in a sales call is gone by the time you need it. Seven of these questions map onto the columns of the matrix below.

1. Whose account sends? Your own account, signed in by you, and where your password goes when you connect it. Every control below protects the account the tool actually runs, so this answer comes first.
2. Where does the session run, and is it the only one? In your browser, in a desktop app on your machine, or on the vendor’s servers. If the vendor runs a session of its own while you stay signed in on your laptop, the account is signed in from two places at the same time.
3. Which IP does the account use? One dedicated to that account, one you bring, a proxy matched to your region, or whatever the vendor’s servers send from.
4. Who sets the daily number? A setting per action that you can lower for one account, a cap the vendor fixes for every customer, or an automatic limit you can’t see. The answer decides whether you can hold a new account, or one coming back from a restriction, below the default.
5. What happens in a new account’s first weeks? A warm-up that starts low and climbs on its own, a ramp you build by hand, or full volume from the first day.
6. When does it send? Days and hours you choose, in the account’s own time zone, or any time the queue has work.
7. Is the gap between actions fixed? Ask whether the tool randomizes the gap between two actions, the number of actions in a day, or both. They are different controls, and a vendor that describes one has told you nothing about the other.
8. Can a person approve a send? Ask whether a message can wait for approval, and whether that holds everywhere you’ll work: the app, the API and the MCP server an AI agent connects through.
9. What does the tool do when LinkedIn refuses an action? Stop that action until its limit resets, pause the account, or keep trying. Vendors describe this in too many different ways to line up in a matrix, so it isn’t one of the columns, and the answer is still worth having in writing. What each restriction notice means is on LinkedIn account restricted.

What a published control looks like

A published control is a sentence on the vendor’s own page that names a setting, says what it does by default and says who can change it. Closely’s working hours are a clean example: by default the account sends “from Monday to Friday between 09:00 AM and 09:00 PM”, and “You can fully customize a schedule in the account settings.” Woodpecker’s hours are fixed, and they still count as published, because the page says exactly when the account works: actions are “sent within fixed hours between 8 AM and 6 PM” on weekdays. Expandi describes its randomized limits with a range you can picture, “between 20 and 27 messages per day”, with the platform picking the exact number.

Read the qualifiers as closely as the numbers, because the careful ones tell you what a number is worth. La Growth Machine says of its action limits, “It’s a maximum, not a guarantee.” FirstTouch asks you to treat any configured limit “as an operational ceiling, not a guarantee”. PhantomBuster labels its own safety limits “recommended, not enforced”, so the volumes it prints are guidance for you to apply, and the tool leaves them to you.

A line in a feature grid that names a control and defines nothing tells you the vendor wants the word on its page. It says nothing about the default, the range or who sets it, and where a vendor stops there, the matrix marks the cell as partly.

What an unpublished control costs you

A control that isn’t written down may still exist. What goes missing is any way to rely on it:

• No way to confirm it. You can’t check that it is switched on for your account, or what it is set to.
• No way to set it. A new account, or one coming back from a restriction, runs at whatever the vendor chose for everyone.
• Nothing to point to. After a restriction, a support ticket has no published commitment to quote back to the vendor.
• No notice when it changes. An unwritten setting can change between two invoices with nothing on the record changing with it.

When two of a vendor’s own pages disagree, the cost is the same, so ask which one the product follows and get the answer in writing. Outcome figures run the other way: they are published and can’t be compared, because one vendor counts users and another counts accounts, the time windows differ or are missing, and none of the figures on the pages we read comes with its method. That is why this page prints none of them and compares controls.

Published controls, vendor by vendor

The 43 tools below are sorted by how many of the eight controls each vendor publishes in its own words, highest first, and alphabetically inside each group. The order is a count of what is on the record. It does not rank how safe a tool is, and a tool lower down may run controls it hasn’t written about. Every tool in the category, on how it runs, its price unit and its API, is on the LinkedIn automation tools list.

Yes means the vendor’s own page describes the control, and the note in brackets gives its scope. Partly means the vendor says something close and stops short, such as a proxy matched to a region or a warm-up it advises and leaves to you, and it doesn’t count toward the total. No means the vendor says it works another way. Not published means we found no statement on the pages read. The words behind every Yes, Partly and No are quoted in the section for that control below, and every page is linked in Sources.

Four products from the same October reading are left out because their own pages put them outside the category: Breakcold says “Breakcold is not a LinkedIn automation software”, Kondo says “Kondo does not automate”, and Captain Data and TexAu sell data and enrichment with no LinkedIn sending of their own on the pages we read.

Randomized timing

Randomized timing means the tool draws the gap between two actions, or the number of actions in a day, at random inside a range, so neither repeats on a fixed schedule. Of the 43 vendors, 19 publish one or the other. Check which one, because a random daily count says nothing about the gaps between sends, and random gaps say nothing about the daily total. How a randomized schedule fits next to a warm-up ramp is laid out step by step in the prevention guide.

• gtm-api.com. Yes, gaps, on bulk runs: “the per-gap interval is randomized between your min and max” (docs, run a mass action).
• Expandi. Yes, daily count: “Expandi lets you set activity ranges with built-in randomization” (help center, daily limits).
• Linked Helper. Yes, gaps: “Linked Helper continuously randomizes the pauses between every micro-step” (safety kit).
• Closely. Yes, daily count: “The number of connection requests and follow-up messages sent is slightly randomized each day.” (help center, daily limits).
• La Growth Machine. Yes, gaps: “Randomizes timing between actions” (LinkedIn limits page).
• We-Connect / We-Link. Yes, daily count: “it will automatically vary the number of actions each day” (help center, randomize).
• Dripify. Yes, gaps: “actions are spaced with randomised timing” (pricing).
• Gojiberry. Yes, gaps: “It spaces actions across your active delivery hours with randomized delays” (help center, safety limits).
• HeyReach. Yes, gaps: “The tool adds a random delay between actions” (help center, working hours).
• LinkedCamp. Yes, gaps: “warms up new accounts and varies timing” (safety page).
• Skylead. Yes, daily count: “The idea is to vary the numbers daily” (help center, global limits).
• Snov.io. Yes, daily count: “Snov.io will randomize the number of actions within that range.” (knowledge base, limits and warm-up).
• Dux-Soup. Yes, gaps, profile visits: “Random intervals control volume of profile visits” (account safety page).
• MeetAlfred. Yes, sessions: “These sessions are staggered and randomized” (help center, how the automation works).
• Reply.io. Yes, daily count: “Dynamic limit ranges pick a random number each day” (docs, LinkedIn limits).
• Waalaxy. Yes, gaps: “semi-random delays between actions” (help center, the queue).
• Alsona. Yes: “daily activity is set from your profile’s age, connections, and history, then spaced and randomized” (pricing).
• ConnectSafely. Yes, gaps: “Random delays and breaks” (security page).
• Salesflow. Partly, delay only: “Each cycle begins with an intentional delay of up to 1 hour” (help center, working hours scheduler).
• ScaliQ. Yes: “automatically randomizes timing and actions” (homepage).
• Botdog. Partly, delays only: “use smart delays between actions” (FAQ).

Settable caps

A settable cap is a number per action, per day or per week, that you can lower for one account without touching the others. It is the control that lets you hold a new account, or one coming back from a restriction, below the vendor’s default. Of the 43 vendors, 23 publish one. Three say they work another way: one sets limits automatically, one fixes them for every customer, and one monitors activity in place of daily limits. The ceilings themselves are on LinkedIn limits, and the limits calculator turns an account’s age, recent limit hits and profile into a daily number per action that you can enter as the cap. What each free tier lets you send is on free LinkedIn automation tools.

• gtm-api.com. Yes, per action: “you can still bound a bucket with target_limit” (docs, smart limits and warmup).
• Expandi. Yes, daily ranges: “You can set your daily outreach limits” (pricing).
• Linked Helper. Yes, daily and hourly: “Configure distinct daily limits and strict hourly pacing” (safety kit).
• Closely. Yes, with warm-up off: “Set your own limits (if you turn off the warm-up)” (help center, daily limits).
• La Growth Machine. Yes, per action: “Action limits let you cap certain activities such as visits, messages, or connection requests.” (help center, limits and work hours).
• We-Connect / We-Link. Yes, per action: “you can set more detailed limits for individual action types” (help center, warm-up and global limits).
• Aimfox. Yes, weekly, per account: “You can set these individually for each connected account” (help center, interaction limits).
• Dripify. Yes, within plan ranges: “you configure your own volumes within these ranges” (pricing).
• Gojiberry. Yes: “you will be able to visualize and modify your limits and schedule” (help center, safety limits).
• HeyReach. Yes, daily: “configure the daily limits per each of the actions” (help center, sending limits).
• LinkedCamp. No, automatic: “Each account’s daily cap follows its age and recent acceptance rate.” (safety page).
• Skylead. Yes, daily: “Set daily action limits for profile views, messages, follows, and more.” (help center, global limits).
• Snov.io. Yes, min and max: “Set a minimum and maximum limit for each action type.” (knowledge base, limits and warm-up).
• Buzz. Yes, account and campaign: “Set account-wide limits for connection requests and profile views” (LinkedIn product page).
• Dux-Soup. Yes, daily: “Pick daily caps for visits, connection requests and messages” (account safety page).
• FirstTouch. Yes, daily: “daily limits match your team’s outreach policy” (docs, safety checklist).
• Linked API. Yes, per action: “Set thresholds for every action type” (safety page).
• MeetAlfred. Yes, daily: “To change the daily maximum allowance for Meet Alfred to run on your account” (help center, daily limits).
• Reply.io. Yes, daily: “View and edit limits under Settings” (docs, LinkedIn limits).
• Waalaxy. Yes, below the plan quota: “you can adjust your quotas in Settings > Account Activity” (help center, quotas).
• CoPilot AI (Yoke). Yes, monthly invites, per campaign: “set the invite allocation to 0” (help center, volume control).
• lemlist. Yes, daily: “set your daily limits for email and LinkedIn” (help center, account limits).
• SalesRobot. Yes, in the API: “Quota Setting” (API reference, quota setting).
• Valley. No, fixed by the vendor: “hard caps (not user-configurable)” (blog, safety).
• Woodpecker. Yes, daily: “you can change how many profile visits, connection requests, or direct messages” (help center, LinkedIn automation).
• LinkupAPI. No, monitoring instead: “We don’t impose blind daily limits.” (homepage).
• Sonarly. Partly, listed only: “Per-sender safety limits” (pricing).
• Unipile. Partly, two pages disagree: “Assign custom quotas per account” (account protection page) and “We don’t enforce any limits on our side” (docs, provider limits).
• OutX. Partly, guidance only: “The pace below is tentative and OutX does not enforce it.” (docs, rate limits).
• PhantomBuster. Partly, guidance only: its safety limits are “recommended, not enforced” (help center, plan limits vs platform limits).

Working hours

Working hours are the days and hours an account is allowed to send, in that account’s time zone. Of the 43 vendors, 18 publish them, and all but one let you set them per account, per sender or per campaign. Woodpecker fixes them, on weekdays from 8 AM to 6 PM in the campaign’s time zone. GTM API’s row reads syncs only: its docs gate recurring syncs by a window and run sends whenever they are triggered, so the column doesn’t count for it.

• gtm-api.com. No, syncs only: “Recurring syncs are window-gated.” and “Actions are not.” (docs, sync windows).
• Expandi. Yes: “Only during the set times and days, the account will be sending” (help center, active times).
• Linked Helper. Yes: “Set Linked Helper activity strictly to your target timezone’s business hours” (safety kit).
• Closely. Yes: “You can fully customize a schedule in the account settings.” (help center, working hours).
• La Growth Machine. Yes: “You can also choose the specific days and hours when your messages can be sent.” (help center, limits and work hours).
• We-Connect / We-Link. Yes: “choose the hours campaigns should run” and “We-Connect pauses all activity during sleep hours” (help center, account safety and sleep hours).
• Aimfox. Yes, per campaign: “Schedules are set on a per-campaign basis” (help center, schedule and timezone).
• Dripify. Yes: “run only inside the working hours you set” (pricing).
• Gojiberry. Yes: “spaces actions across your active delivery hours” (help center, safety limits).
• HeyReach. Yes, per sender: “You can configure working hours and time zone for every sender per campaign.” (help center, working hours).
• Skylead. Yes: “Adjust your start and end times” (help center, working hours).
• Buzz. Yes: “set your time zone and work hours” (LinkedIn product page).
• Dux-Soup. Yes: “Set your own custom working hours” (account safety page).
• FirstTouch. Yes, per sender: “the sender’s Work Schedule and time zone are correct” (docs, safety checklist).
• MeetAlfred. Yes: “you have the flexibility to adjust these hours” (help center, working hours).
• Waalaxy. Yes: “Actions will start sending during your configured working hours” (help center, the queue).
• SalesRobot. Partly, schedule setting only: “blacklist, schedule, quota, and pending invite management” (API reference, quota setting).
• Woodpecker. Yes, fixed, weekdays: “sent within fixed hours between 8 AM and 6 PM” (help center, LinkedIn automation).
• Salesflow. Yes: “The working hours ensure any campaign actions are sent between a specific time” (help center, working hours scheduler).
• Zeekeo. Yes: “You choose which days and times your campaign is active.” (academy, campaign settings).

Warm-up

A warm-up starts a newly connected account below its full allowance and raises it over the first days or weeks without you setting each step. Of the 43 vendors, 12 publish one. Check two things in the wording: whether the ramp covers every action or only invitations, and whether the vendor runs it or only advises it. A ramp you have to build by hand from lower caps is advice, and the matrix marks it as partly.

• gtm-api.com. Yes, automatic: “A freshly connected account starts with reduced budgets that ramp up gradually.” (docs, smart limits and warmup).
• Expandi. Yes, 14 days or custom: “You can use a gradual warm-up (14-day warm-up) option or a custom one” (help center, account warm-up).
• Closely. Yes, on by default: “we’ll be gradually increasing the amount of sent requests” (help center, warm-up period).
• We-Connect / We-Link. Yes: “We-Connect will automatically adjust the action limits from your campaigns to the warm-up settings.” (help center, warm-up and global limits).
• Aimfox. Yes, optional: “Optional Warm-Up Period” and “begin at a slower pace during the initial phases” (help center, pacing).
• LinkedCamp. Yes, automatic: “New accounts start at about 10 invitations a day and ramp over 4 weeks” (safety page).
• Skylead. Yes, automatic: “Every new Skylead account starts off in Warmup Mode.” (help center, warmup mode).
• Snov.io. Yes, invitations: “ramp up connection requests gradually” (knowledge base, automatic warm-up).
• Buzz. Partly, advice: “Start new or reactivated accounts on lower limits and ramp up over time” (LinkedIn product page).
• FirstTouch. Partly, advice: “Begin with low daily activity.” (docs, safety checklist).
• ConnectSafely. Partly, limits by account age: “Conservative daily limits based on account age and activity” (security page).
• CoPilot AI (Yoke). Yes, automatic: “your account enters a warm-up period” (help center, warming up).
• lemlist. Yes, invitations only: “Ramp-Up starts invitations at a lower daily volume.” and “Ramp-Up only covers invitations.” (help center, invitation ramp-up).
• AiSDR. Yes, automatic: “the account enters an automatic ramp-up stage” (help center, LinkedIn limitations).
• Edges. Yes, automatic: “A newly connected identity does not receive its full allowance immediately” (docs, LinkedIn limits).
• Sonarly. Partly, name only: “Built-in warm-up” (pricing).

A review step before anything sends

A review step puts a person between a drafted action and the send: a message waits for approval, or a batch shows a preview that someone has to confirm before it runs. Of the 43 vendors, 12 publish one. Several publish it for the MCP server only, the surface an AI agent connects through, so check that the scope matches the way you’ll actually work.

• gtm-api.com. Yes, MCP, and bulk runs in the API: “Outward actions (sends, bulk dispatches) return a preview and require an explicit confirmation step” (docs, MCP overview).
• Expandi. Yes, MCP: “It drafts, you approve.” (MCP page).
• Linked Helper. Yes, app: “Generated messages wait in a drafts queue for your approval” (pricing).
• La Growth Machine. Yes, MCP: “Claude and ChatGPT ask for your approval before sending a message” (MCP page).
• Gojiberry. Yes, app: “Full auto or approve before it sends” (homepage).
• LinkedCamp. Yes, app and MCP: “Anything that reaches a prospect waits for approval.” (homepage).
• Dux-Soup. Partly, MCP tool permissions: “you can manage permissions for the tools it can use” (MCP guide).
• FirstTouch. Yes, MCP: “review generated content, approve outreach” (docs, MCP overview).
• Reply.io. Yes, preview before launch: “Preview every automatic step before launch” (docs, LinkedIn capabilities).
• Alsona. Yes, app: “Nothing sends without your sign-off.” (pricing).
• Valley. Yes, MCP: “approval gates on everything that touches a prospect” (MCP page).
• Sonarly. Yes, app: “approve every message and email before it gets sent out” (homepage).
• Taplio. Yes, MCP, posts and replies: “Nothing posts until you confirm.” (MCP page).

An IP or proxy per account

An IP or proxy per account means each connected account sends from an address of its own, or from one you bring, and keeps it. Of the 43 vendors, 20 publish it. A proxy matched to a region or picked by location, with no statement that it belongs to that account alone, is marked as partly. What changes when one person runs several accounts is on scaling LinkedIn automation.

• gtm-api.com. Yes, dedicated: “Dedicated residential proxies” and “Per account, managed for you.” (pricing).
• Expandi. Yes, dedicated: “Everyone in Expandi gets their personal dedicated IP address” (help center, IP address and proxy).
• Linked Helper. Yes, per account: “Linked Helper allows you to bind a dedicated proxy to each account instance” (safety kit).
• Closely. Yes, dedicated: “Dedicated residential IP for each Linkedin account” (pricing).
• La Growth Machine. Yes, dedicated, per user: “each of our users gets a dedicated IP” (safety page).
• We-Connect / We-Link. Yes, dedicated: “Dedicated country-based IP address” (We-Connect pricing) and “Every account gets a dedicated, geo-matched IP” (We-Link homepage).
• Aimfox. Yes, bring your own: “Bring-your-own IPs” (pricing).
• Dripify. Yes, dedicated: “a consistent IP address tied to your account, in your location” (pricing).
• Gojiberry. Partly, login region: “We use proxies that match your usual login region” (help center, restrictions).
• HeyReach. Yes, entry plan, your own above it: “provides a dedicated residential proxy to each of the LinkedIn senders” and “require you to bring your own proxies” (pricing).
• LinkedCamp. Yes, per account: “a dedicated IP per account” (homepage).
• Skylead. Partly, login country: “Skylead uses a proxy from your original login country” (help center, proxies).
• Snov.io. Yes, dedicated: “Each slot includes a dedicated proxy.” (knowledge base, connecting an account).
• Buzz. Yes, location or your own: “Choose the location your account runs from when you connect it, or use your own proxy.” (LinkedIn product page).
• Linked API. Yes, stable residential: “We maintain a stable residential IP from your region” (safety page).
• ConnectSafely. Yes, dedicated: “Dedicated proxy assignment per account” (security page).
• SalesRobot. Yes, dedicated: “dedicated IPs for each LinkedIn account” (homepage).
• Valley. Yes, dedicated: “Valley uses dedicated IP addresses per account (not shared)” (blog, safety).
• LinkedFusion. Yes, dedicated: “Get Dedicated local IP address for your LinkedIn Account.” (homepage).
• LinkupAPI. Yes, own, or bring your own: “Every account gets its own residential or ISP IP” (homepage).
• Salesforge. Yes, your own, or shared by default: “Salesforge allows you to add and configure your own proxy settings” and “routed via high-quality shared proxies” (help center, account protection).
• Unipile. Yes, fixed per account: “We assign fixed IP to each account” (account protection page).
• Zeekeo. Partly, location chosen at connection: “you will be asked to choose a proxy location” (academy, connecting an account).

One session per account

One session per account means the account is signed in from one place, and the automation drives that session with no second one opened next to yours. Of the 43 vendors, two state it outright: GTM API names it on its pricing page, and Linked Helper says the session lives on your own machine and “never on our servers”. Browser extensions run inside your own session by design, and the two that describe where they run are marked as partly, because neither says the session is the only one.

• gtm-api.com. Yes, named: “Single Session Protection” (pricing).
• Linked Helper. Yes, on your machine: “Where your LinkedIn session lives” and “never on our servers” (pricing).
• ConnectSafely. Partly, isolated, location unpublished: “Isolated browser sessions” (security page).
• Octopus CRM. Partly, runs in your browser: “we’ll never ask for your LinkedIn credentials” (homepage).
• OutX. Partly, runs in your browser: “OutX runs through the Chrome extension installed on your browser.” (docs).

A cloud browser per account

A cloud browser per account means each connected account gets a browser of its own on the vendor’s servers, which you sign in to yourself, so the automation runs without your laptop and without a browser shared between accounts. Of the 43 vendors, two publish it in those terms.

• gtm-api.com. Yes: “Accounts connect through a real cloud browser” (pricing).
• Linked API. Yes: “Each LinkedIn account gets its own full browser in the cloud” (safety page).
• Waalaxy. Partly, cloud, no browser per account stated: “Waalaxy is now 100% cloud” (help center, fully cloud based).

Frequently Asked Questions

Sources

• gtm-api.com, docs, run a mass action · docs, smart limits and warmup · docs, sync windows · docs, MCP overview · pricing, read 2026-10-14 (our own pages)
• Expandi, help center, daily limits · pricing · help center, active times · help center, account warm-up · MCP page · help center, IP address and proxy, read 2026-10-14
• Linked Helper, safety kit · pricing, read 2026-10-14, re-checked 2026-10-27
• Closely, help center, daily limits · help center, working hours · help center, warm-up period · pricing, read 2026-10-14
• La Growth Machine, LinkedIn limits page · help center, limits and work hours · MCP page · safety page, read 2026-10-14, re-checked 2026-10-27
• We-Connect / We-Link, We-Connect pricing · We-Link homepage · help center, randomize · help center, warm-up and global limits · help center, account safety · help center, sleep hours, read 2026-10-14, re-checked 2026-10-27
• Aimfox, help center, interaction limits · help center, schedule and timezone · help center, pacing · pricing, read 2026-10-14
• Dripify, pricing, read 2026-10-14
• Gojiberry, help center, safety limits · homepage · help center, restrictions, read 2026-10-14
• HeyReach, help center, working hours · help center, sending limits · pricing, read 2026-10-14
• LinkedCamp, homepage · safety page, read 2026-10-14, re-checked 2026-10-27
• Skylead, help center, global limits · help center, working hours · help center, warmup mode · help center, proxies, read 2026-10-14
• Snov.io, knowledge base, limits and warm-up · knowledge base, automatic warm-up · knowledge base, connecting an account, read 2026-10-14, re-checked 2026-10-27
• Buzz, LinkedIn product page, read 2026-10-14, re-checked 2026-10-27
• Dux-Soup, account safety page · MCP guide, read 2026-10-14
• FirstTouch, docs, safety checklist · docs, MCP overview, read 2026-10-14
• Linked API, safety page, read 2026-10-14
• MeetAlfred, help center, how the automation works · help center, daily limits · help center, working hours, read 2026-10-14
• Reply.io, docs, LinkedIn limits · docs, LinkedIn capabilities, read 2026-10-14
• Waalaxy, help center, the queue · help center, quotas · help center, fully cloud based, read 2026-10-14, re-checked 2026-10-27
• Alsona, pricing, read 2026-10-14, re-checked 2026-10-27
• ConnectSafely, security page, read 2026-10-14
• CoPilot AI (Yoke), help center, volume control · help center, warming up, read 2026-10-14
• lemlist, help center, account limits · help center, invitation ramp-up, read 2026-10-14
• SalesRobot, API reference, quota setting · homepage, read 2026-10-14
• Valley, blog, safety · MCP page, read 2026-10-14
• Woodpecker, help center, LinkedIn automation, read 2026-10-14
• AiSDR, help center, LinkedIn limitations, read 2026-10-14
• Edges, docs, LinkedIn limits, read 2026-10-14
• LinkedFusion, homepage, read 2026-10-14
• LinkupAPI, homepage, read 2026-10-14
• Salesflow, help center, working hours scheduler, read 2026-10-14
• Salesforge, help center, account protection, read 2026-10-14
• ScaliQ, homepage · pricing, read 2026-10-14, re-checked 2026-10-27
• Sonarly, pricing · homepage, read 2026-10-14
• Taplio, MCP page, read 2026-10-14
• Unipile, account protection page · docs, provider limits, read 2026-10-14
• Zeekeo, academy, campaign settings · academy, connecting an account, read 2026-10-14
• Botdog, FAQ, read 2026-10-14
• Leadspicker, pricing, read 2026-10-14, nothing found for any of the eight controls
• Octopus CRM, homepage, read 2026-10-14
• OutX, docs · docs, rate limits, read 2026-10-14, re-checked 2026-10-27
• PhantomBuster, help center, plan limits vs platform limits, read 2026-10-14
• Left out of the matrix by their own pages: Breakcold, help center · Kondo, homepage · Captain Data, pricing · TexAu, homepage, read 2026-10-14
• Related: LinkedIn automation hub · LinkedIn automation tools list · Free LinkedIn automation tools · Safe LinkedIn automation · How to avoid getting banned on LinkedIn · LinkedIn limits · LinkedIn limits calculator · Scaling LinkedIn automation · LinkedIn account restricted

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