> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn action limits, schedule and ramp-up

> Why a new LinkedIn account sends less than its limit, what each action cap means, and how the sending window works.

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

A LinkedIn account carries a daily and a weekly cap on each of the four kinds of activity its
settings page controls: connection requests, messages, InMail and profile views. A newly
connected account is held below those numbers and steps up to them over its first weeks, because
starting at full volume on day one is one of the strongest signals LinkedIn uses to spot an
automated account.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Integrations<span className="pl-path__sep">→</span>LinkedIn Account</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to LinkedIn Account <code>read-linkedin-accounts</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-linkedin-accounts</code> to add one, <code>update-linkedin-accounts</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your plan</div>
    <div className="pl-availability__value">Needs at least one seat for LinkedIn accounts.</div>
  </div>

  <div className="pl-availability__note">Not listed in the sidebar today; reachable from the surfaces that link to it, and by URL. If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

## How it behaves

### Four action types, each with a recommended value and a hard limit

The **Action Limits** step on an account's settings page lists four cards (**Connection
Requests**, **Messages**, **InMail** and **Profile Views**), each with a **Daily Limit** and a
**Weekly Limit** field. The two numbers behind each field come from the account's own type
(**LinkedIn Basic**, **LinkedIn Premium**, **Sales Navigator** or **LinkedIn Recruiter**), and the
type is read from the LinkedIn account itself when it connects, not something you pick.

Under every field is a helper line naming a recommended value and a hard limit (1). The fields
arrive already filled with the recommended value for the type that was detected, and a field you
empty falls back to that same value. The hard limit is a ceiling rather than a suggestion: a
bigger number is rejected, and the form will not save until you bring it back down. Basic tops
out at 25 connection requests a day; Sales Navigator goes up to 45.

**InMail** is the one exception (2): on a Basic account its **Daily Limit** and **Weekly Limit**
fields are disabled, and the card carries a **Not available on Basic** chip in place of the usual
limits. Premium, Sales Navigator and Recruiter accounts all have an InMail allowance.

Whatever number ends up in effect (yours, or the recommended value behind a field you left
empty) is what the ramp-up below scales down while the account is new. It is not only the
recommended figure that shrinks.

Reactions and comments on leads' posts draw on caps from the same table, for agents set up to do
them. Those two have no fields on this screen.

<Screenshot id="channels/linkedin-limits-and-ramp-up--limit-cards" frame="bare" alt="The four action-limit cards on a LinkedIn account's settings page: Connection Requests, Messages, InMail and Profile Views. Connection Requests, Messages and Profile Views each show a Daily Limit and Weekly Limit field with a hard-limit chip and a Recommended and Hard limit helper line. The InMail card is dimmed, its fields disabled, with a Not available on Basic chip in place of the usual limits." caption="Both numbers come from the account's own type: Basic here, so InMail stays out of reach until the LinkedIn account is upgraded." marks={[{ n: 1, x: 76, y: 32 }, { n: 2, x: 27, y: 74 }]} />

The same step also sets a **Delay Between Actions**, in seconds: **Min Delay (seconds)** and
**Max Delay (seconds)**. After a profile view, an invitation or a message, the account starts a
pause of a length drawn from that range, and the next action of any kind waits for the pause to
run out.

### New accounts step up to their limits over three weeks

A LinkedIn account does not run at those numbers from the day it connects. It starts at a
fraction of them and climbs in steps, and the last step (full volume) arrives before the three
weeks are up.

While it is ramping, a banner at the top of the account's page says the account is warming up,
which day of the ramp it is on out of 21 (1), what percentage of the limits below it is sending
at, and how far through it is (2). The accounts list shows the same percentage as a small
warming-up chip on that account's row. Because the final step is full volume, an account can read
100% in that banner and still be counted as warming up. Once day 21 has passed the banner
disappears for good and the numbers on the cards apply in full. They are ceilings, not targets:
the volume actually planned for a given day is drawn below the daily limit, so even a fully
ramped account usually stops short of it.

The scale-down never rounds a live action type down to zero. Any limit above zero stays at a
minimum of one action a day, however early in the ramp the account is. InMail on a Basic account
is the exception, because its limit is zero to begin with.

<Screenshot id="channels/linkedin-limits-and-ramp-up--ramp-notice" frame="bare" alt="A banner headed Warming up with the current ramp day out of 21, a line saying the account is currently sending at a percentage of the limits below and will reach full volume gradually, and a progress bar underneath" caption="A representative example: the account in these screenshots finished its ramp long ago, so this banner is simulated." marks={[{ n: 1, x: 50, y: 22 }, { n: 2, x: 50, y: 88 }]} />

### Fewer than 150 connections pauses new outreach

An account with fewer than 150 connections has too thin a network to be doing cold outreach, so
it stops picking up new leads: the profile view that opens a new lead never happens.
Replies and follow-ups in conversations that are already running are untouched. The account shows
a **Low connections** chip in the list and a warning on its own page saying the same thing:
outreach to new leads is paused until the network grows, replies to existing conversations still
send. A connection count that has never been read is not treated as low; only a known count under
150 holds anything back.

### Actions queue instead of firing immediately

When an agent works a new lead it views the lead's profile first and sends the connection request
in a later run, hours after that view rather than straight afterwards. An invitation nobody
accepts does not stay open forever either: once it is 14 days old the account withdraws it, and
the lead lands on **Withdrawn**, the last of the five stages on the account's
**Automation Pipeline** card, after **Warming Up**, **Invited**, **Connected** and **Messaging**.
Those five stages belong to that card. They are not the lead's own stage.

That 14 days is a default you can change for the whole workspace, alongside the other LinkedIn
timings, under [workspace-wide pacing](/en/ai-agents/campaign-pacing-settings).

### The schedule decides which hours the account acts in

The **Schedule** step on the same settings page holds an **Account timezone** and a grid of the
days and hours the account may act in. Those windows are wall-clock times in that time zone,
never your browser's, so the hours you set are the hours the account works.

A schedule is not optional in practice. Campaign automation only picks up an account whose own
local time falls inside one of its windows, and a queued LinkedIn action checks the same thing
before it fires, so an account left with no windows at all never acts. That is why one is
created for it when it connects: Monday to Friday, a morning block and an afternoon block, yours
to change.

Once an active account has a schedule, its row in the accounts list gets a calendar button in the
**Schedule** column. It opens today's actual slots: the specific times the account plans to act,
not the blocks you set. Those appear as a 24-hour dial (1) beside a list of those times (2),
invitation slots and message slots in separate colours, with the next one still to come marked
apart from the rest.

<Screenshot id="channels/linkedin-limits-and-ramp-up--schedule" frame="bare" alt="The schedule popover open from a LinkedIn account row: a 24-hour clock face with coloured dots marking invitation and message slots, and a list of those times beside it with the next one labelled NEXT" caption="A representative example: the account in these screenshots has no schedule set, so the windows here are simulated." marks={[{ n: 1, x: 27, y: 45 }, { n: 2, x: 75, y: 45 }]} />

<Note>
  The dial and the time list, including the label marking the next slot, are shown in English on
  every language setting. Only the status line underneath, when one shows, is translated.
</Note>

### Even a fully ramped account can sit out a day

On top of the caps and the ramp, an account takes the odd day off at random: no profile views,
no invitations, no messages that day. It is why a healthy, fully ramped account can show zero
actions on an ordinary working day; on a day like that the schedule popover reports no time
windows for today at all. That is the pattern doing its job, not an error.

## Limits

|                                  |                                                                                                                                                               |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Metered on the settings page     | Connection requests, messages, InMail, profile views: each with its own daily and weekly cap. Post reactions and comments are capped too, without fields here |
| InMail                           | Not available on Basic; allowed from Premium up                                                                                                               |
| Connection-request ceiling       | 25 a day on Basic, up to 45 on Sales Navigator                                                                                                                |
| Minimum connections for outreach | 150: below that the account stops picking up new leads; replies still send                                                                                    |
| Ramp-up                          | Runs to day 21 after connecting; the last step restores full volume before that                                                                               |
| Unanswered invitation            | Withdrawn once it is 14 days old: a workspace-wide setting, 14 days by default                                                                                |
| Schedule                         | Required in practice: an account with no windows never acts. One is created when it connects                                                                  |
| Random day off                   | A small chance on any day, ramped or not                                                                                                                      |

## Related

<CardGroup cols={2}>
  <Card title="Connect a LinkedIn account" icon="link" href="/en/channels/connect-linkedin-account">
    Set up the account these limits and this ramp-up apply to.
  </Card>

  <Card title="LinkedIn Chat" icon="messages-square" href="/en/channels/linkedin-chat">
    Where the messages this page's limits govern actually show up.
  </Card>

  <Card title="Why the agent's daily sending numbers move" icon="gauge" href="/en/ai-agents/sending-limits">
    How an agent's LinkedIn budget is read from this account's limits and ramp step.
  </Card>

  <Card title="Resting days, sending windows and deferrals" icon="calendar-days" href="/en/email-accounts/resting-days-and-schedule">
    The equivalent schedule and pacing mechanics on the email side.
  </Card>
</CardGroup>
