# How LinkedIn action limits work

> The daily caps Reply applies to automatic LinkedIn steps — dynamic ranges vs a static maximum, the nine action types, the 100-per-action ceiling, and what happens when a cap is hit.

**Reply caps each automatic LinkedIn action type per day, across nine action types. Dynamic limit ranges pick a random number each day (suggested 25-35 for most actions, 35-50 for messages); the static mode uses one fixed number, 30 by default. Any limit can be raised to 100. A hit limit pauses that action until the next day.**

_Status: Reviewed — human-edited, facts not yet confirmed against the product._

## At a glance

| Aspect | Detail |
| --- | --- |
| **What it governs** | How many automatic LinkedIn actions Reply performs per day, per connected LinkedIn account and per action type |
| **Trigger** | Each executed automatic LinkedIn step counts toward its action type's daily limit |
| **Inputs** | Limit mode (limit ranges or max amount), the per-action values, and the number of actions completed today |
| **Result** | When a cap is reached, that action pauses for the rest of the day and resumes the next day |
| **Configurable** | Yes — per action type, up to 100 per day; edits take effect starting the next day |
| **Does not** | Count manual LinkedIn actions, raise LinkedIn's own platform caps (such as its weekly connection-request limit), or pause other action types when one hits its cap |

## Rule summary

Reply's algorithm monitors the connected [LinkedIn account](/how-to/connect-linkedin) and
sets recommended safe limits for each action type. There are two limit modes. **Limit
ranges (dynamic limits)** let you set a range for daily actions, and Reply picks a random
number from that range each day — for example, with a 20–30 range Reply might send 22
requests on day 1, 28 on day 2, 25 on day 3. Varying the daily count makes activity look
more natural to LinkedIn and reduces the risk of the account being flagged. **Max amount
(static limit)** is one fixed daily number per action; the default is **30** for each
LinkedIn action. Every limit can be set up to **100** per action. When a daily cap is
reached, Reply pauses that action, notifies you in the sequence **Log** tab, and resets
everything the next day.

## Trigger

Every automatic LinkedIn step a sequence executes — a connection request, message,
profile view, and so on — increments the daily counter for its action type. The number of
actions completed today appears in the top right corner of each action on the LinkedIn
account's settings page. Manual actions are not included.

The nine action types you can set limits for:

| Action type | What it covers | Suggested dynamic range |
| --- | --- | --- |
| Connections | Connection requests, including the short note sent with them | 25–35 |
| View Profile | Automatic profile views for contacts | 25–35 |
| Like Recent Posts | Liking posts from your targeted contacts | 25–35 |
| Messages | Direct messages to LinkedIn contacts | 35–50 |
| InMail | Private messages to LinkedIn users without a prior connection | 25–35 |
| Detections | The number of times daily Reply checks LinkedIn threads for prospects' replies | 25–35 |
| Revoke Connections | Cancelling unaccepted connection requests | 25–35 |
| Endorse Skills | Endorsing contacts' skills automatically | 25–35 |
| Follow Profile | Following targeted LinkedIn profiles | 25–35 |

## Decision logic

1. Determine today's cap for each action type — a random number from the configured range in dynamic mode, or the fixed value in static mode.
2. Each executed automatic action increments its action type's daily counter.
3. When a counter reaches the cap, Reply pauses that action type. Other action types keep running.
4. A notification is posted in the **Sequence → Log** tab.
5. The next day, counters reset and the sequence automatically attempts the postponed LinkedIn steps again. Limit counters reset according to the UTC time zone.

LinkedIn's own limits apply in parallel: a sequence can pause connection steps because of
LinkedIn's weekly connection-request cap even when the Reply limit has not been reached,
and free LinkedIn accounts can send only **3** personalized connection requests (with a
note) per month.

## Result

Hitting a Reply limit is routine, not an error. The affected action is postponed until
the next day, you get a Log-tab notification, and everything resets — no contacts are
lost and no steps are cancelled. If you saved automatic LinkedIn steps and ran the
sequence but hit the daily limits, execution is simply postponed until the next day.

## State changes

| Field | Change |
| --- | --- |
| Daily action counter | Increments per executed automatic action; visible in the top right corner of each action |
| On reaching a cap | That action type pauses until the next day |
| Sequence Log | A notification records that the limit was reached |
| Next day | Counters reset (UTC); postponed steps are attempted again automatically |

## Exceptions

- **Manual actions never count.** The limits apply only to LinkedIn automatic steps.
- **LinkedIn platform caps are independent.** LinkedIn enforces its own weekly connection-request limit, allows free accounts only 3 personalized requests (with a note) per month, and caps every account at 30,000 first-degree connections — after which the Connect button becomes a Follow button.
- **Detections are themselves limited.** Reply's daily checks of LinkedIn threads for prospects' replies count against the Detections limit.
- **Endorse Skills endorses no more than 3 skills per contact** in Reply.
- **Connection acceptance can be detected across accounts.** With multiple LinkedIn accounts connected in a Team, an accepted request can be detected from any of them, based on the Team's connected accounts and the prospect's profile URL.

## Configuration that changes this rule

View and edit limits under **Settings → LinkedIn Accounts** — click the connected
account, pick a mode (Limit ranges or Max amount), move the slider for each action, and
save. Changes take effect starting the next day; for the rest of the current day, actions
follow the previously set limits.

The **Revoke connection requests** setting adds an automatic clean-up rule: when enabled,
all sent requests are checked every day, and any request still unaccepted after the
configured timeframe is revoked. The default timeframe is 7 days; the minimum is 1 day
and the maximum is 180. Automatic revokes are governed by the Revoke Connections daily
limit. A revoked request cannot be re-sent to the same person for up to 3 weeks.

LinkedIn does not publicly disclose its own limits; the figures below are Reply's
recommendations based on testing and experience, and they vary by LinkedIn plan and by
your Social Selling Index (SSI) — LinkedIn's score for how credibly you use the platform:

| Action | Free account | Sales Navigator | Premium |
| --- | --- | --- | --- |
| Connection requests | Up to 100 per week | 100–150 weekly; up to 200 with a higher SSI | 100–150 weekly; up to 200 with a higher SSI |
| Messages | 20–30 per day | 50–70 per day | 30–50 per day |
| InMails | Not available | Typically 50 InMail credits per month | Not supported in Reply |
| Profile views | 50–100 per day | 100 per day | 100 per day |
| Likes | 50–100 per day | 100 per day | 100 per day |
| Endorsements | 20–30 per day | 50–70 per day | 30–50 per day |
| Profile follows | Up to 200 per day | 300–500 per day | 200–300 per day |
| Revoking connections | 20–30 per day | 50–70 per day | 30–50 per day |

Reply's per-action ceiling of 100 per day applies regardless, so recommendations above
100 (for example, profile follows) are capped at 100 in practice.

> To raise limits safely: warm up slowly (start with 10–15 connection requests per day and
> increase to 20–30 after a week or two), personalize requests, and alternate automated
> steps with manual activity. An acceptance rate below 30–40% signals irrelevant outreach
> to LinkedIn and increases the risk of restrictions — track it in sequence stats or
> LinkedIn reports.

## Limits

| Limit | Value |
| --- | --- |
| Suggested dynamic range — connections, views, likes, InMails, detections, revokes, endorsements, follows | 25–35 per day |
| Suggested dynamic range — messages | 35–50 per day |
| Static (max amount) default | 30 per action per day |
| Maximum configurable limit | 100 per action type per day |
| When limit edits apply | The next day |
| Counter reset | Daily, per the UTC time zone |
| Free accounts — personalized connection requests (with a note) | 3 per month |
| First-degree connections per LinkedIn account | 30,000 (LinkedIn platform cap) |
| Connection-request note | 200 characters (free), 300 characters (Premium and Sales Navigator) |
| LinkedIn message | 8000 characters |
| InMail | 200-character subject line, 1900-character body |
| Skills endorsed per contact | Up to 3 |
| Revoke window for unaccepted requests | 1–180 days, default 7 |

## FAQ

### What happens when a daily limit is reached?

Reply pauses that action type and posts a notification in the **Sequence → Log** tab.
Nothing is lost — counters reset the next day and the sequence attempts the postponed
steps automatically during its schedule. See
[Why LinkedIn steps fail](/troubleshooting/linkedin-steps-fail) for the other reasons a
LinkedIn step can stop.

### Do manual LinkedIn actions count toward the limits?

No. The limits apply only to LinkedIn automatic steps and do not include any manual
actions you perform yourself.

### Why did connection requests stop before my Reply limit was reached?

LinkedIn enforces its own limits alongside Reply's — most notably a weekly
connection-request cap — and free accounts can send only 3 personalized requests (with a
note) per month. Compare your account limits with today's action count in LinkedIn
reports, and see [Why LinkedIn steps fail](/troubleshooting/linkedin-steps-fail).

### Should I set every limit to 100?

Not recommended. Dynamic ranges mimic natural behavior better than a maxed-out static
cap, and exceeding what LinkedIn tolerates can lead to account restrictions. Warm up
gradually and keep the acceptance rate healthy — below 30–40% increases restriction risk.

## Related

- [Why LinkedIn steps fail](/troubleshooting/linkedin-steps-fail) — the full error taxonomy when steps stop
- [LinkedIn outreach](/capabilities/linkedin-outreach)
- [Connect LinkedIn](/how-to/connect-linkedin)
- [Sending schedules](/behavior/sending-schedules) — automatic LinkedIn steps follow the sequence schedule
- [Limits](/reference/limits)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) — sequence and account operations
- MCP: [agents.reply.io/mcp](https://agents.reply.io/mcp) — LinkedIn safety-limit and account management for agents