Use the Competitor connections signal in Signal Agents to see when your competitors’ sales reps add new LinkedIn connections. This helps you spot who they’re actively prospecting so you can react quickly with timely, relevant outreach.
Learning objective
By the end of this tutorial, you’ll know how to create a Signal Agent that monitors competitors’ new LinkedIn connections, control daily volume with a cap, and decide how identified signals should be processed in your workflow.
Why this matters
New connections are a strong intent signal: they often indicate active prospecting into new accounts, territories, or personas. Monitoring these connections helps you prioritize outreach while the competitor’s activity is still fresh.
Prerequisites
You have access to Signal Agents and can create a new Signal Agent.
You have the competitor’s LinkedIn company URL (required for setup).
You have enough credits available (billing is based on identified signals).
Core lesson — Step-by-step workflow
Phase 1: Create a new Signal Agent and choose the right signal
Go to Signal agents, then click Create signal agent.
In Select a signal to detect, expand Buyer intent and choose Competitor connections.
This tells lemlist to track when competitor reps expand their LinkedIn network with new connections.
Phase 2: Configure the competitor(s) to monitor
Add one or more LinkedIn company URLs (one per line), then click Add company URLs.
Adding the company page URL is required—this is how the signal knows which competitor organizations to track.
Phase 3: Define the scope and control volume
In the Scope step, keep All segments if you want to retrieve all contacts that trigger the signal, or use the available filters to narrow the audience.
Set the Maximum number of signals identified per day.
This cap helps you control both volume and spend. As signals are identified, costs are calculated based on your daily limit.
Phase 4: Decide what happens when signals are found
In Signals processing, choose how you want to handle identified signals:
Review signals manually to assess them case by case
Auto-create tasks for identified signals
Auto-push to campaign for automated follow-up
If you choose tasks, configure details like task type, owner type, fallback owner, priority, and clear instructions for your team.
If you prefer automation, choose Auto-push to campaign, then select the campaign and review the import settings before continuing.
How it works (behind the scenes)
You pick the Competitor connections signal type in Signal Agents.
You add the competitor’s LinkedIn company URL (required).
You define the scope and set a daily cap to control volume.
lemlist ingests new connections and reconciles profiles with the People database.
Billing: 100 credits per identified signal.
Signal details (what you’ll receive)
Each identified signal can include:
Job title
Company
Headline (if available)
Location
LinkedIn URL of the new connection
Who they connected with (when available)
Practical application (example workflow)
If a competitor’s SDR connects with multiple heads of RevOps in one week, treat it as a persona focus shift:
Auto-create a task for each identified connection.
Task instruction example: “Check if this contact is in our ICP. If yes, add to the ‘RevOps—Competitive’ campaign and personalize the opener referencing their role.”
Prioritize by seniority (e.g., Director+ first) and region (match your territory).
Troubleshooting & pitfalls
Issue: No signals are being identified
Root cause: Incorrect LinkedIn company URL format, or the competitor has low connection activity.
Fix: Ensure you’re using the company page URL (e.g., https://www.linkedin.com/company/companyname/) and try monitoring additional competitors.
Issue: Too many signals per day
Root cause: Daily cap is set too high for your team’s capacity or budget.
Fix: Lower the Maximum number of signals identified per day and use the filters in the Scope step to narrow results.
Issue: Signals found but not acted on
Root cause: Processing is set to manual without a follow-up routine, or tasks aren’t assigned clearly.
Fix: Switch to Auto-create tasks, set Owner type, and define a fallback owner so nothing is missed.