LinkedIn Activity Limits

What it is

The safety governor for automated LinkedIn activity. One row per day holds running counters of everything the agents did on LinkedIn — connection requests, profile views, searches, messages, withdrawn invites — against a daily_budget. When a counter approaches its ceiling the row accumulates warnings, and the agents back off. This is what keeps automated LinkedIn activity within limits that look human and stay inside LinkedIn’s tolerances.

Fields

Field	Type	Description
`date`	date	The day these counters cover (one row per day)
`connection_requests`	integer	Connection requests sent today
`profile_views`	integer	Profiles viewed today
`search_calls`	integer	LinkedIn searches run today
`messages_sent`	integer	Messages sent today
`invites_withdrawn`	integer	Pending invites withdrawn today
`daily_budget`	integer	The day’s overall activity ceiling
`warnings`	array	Warnings raised as counters approach their limits
`last_updated`	datetime	When the counters were last touched
`department_id`	uuid	Owning department, for visibility scoping

Also carries the system columns id, tenant_id, and workspace_id (tenant isolation). They are managed automatically.

{ "method": "tools/call", "params": { "name": "data_query", "arguments": { "view_slug": "linkedin_rate_tracker", "select_fields": ["date", "connection_requests", "messages_sent", "daily_budget", "warnings"], "sort_by": "date", "limit": 30 } } }

Getting Started

Resources

Sales & Commerce

Procurement

Marketing & Outreach

Governance

LinkedIn Activity Limits

What it is

How it gets data

Fields

Query it

​What it is

​How it gets data

​Fields

​Query it

What it is

How it gets data

Fields

Query it