Connecting multiple LinkedIn profiles to a central sending system is notoriously difficult. LinkedIn monitors where you log in from and frequently issues security checkpoints—such as OTP codes or push approvals—to verify it’s actually you.
OutFlo’s backend is designed to handle these security checkpoints smoothly, allowing you to connect accounts securely and keep them online. This guide covers how to solve connection issues, handle multi-factor authentication (MFA), and configure proxies.
1. Understanding the Asynchronous Login Flow
When you log in manually or via our API, OutFlo initializes a secure, dedicated browser instance in our cloud infrastructure. Because LinkedIn checks your location, the connection process is designed as an asynchronous 3-step loop:
- 1.Initiate Login: Submit your username (email/phone) and password. OutFlo boots a secure session using residential proxies close to your physical location.
- 2.Solve Checkpoint (If prompted): LinkedIn will often challenge the new device. We capture the challenge state (OTP, 2FA, or Mobile App Validation) and display a dedicated input block.
- 3.Poll for Status: Once resolved, OutFlo configures your dashboard workspace, downloads your profile credentials, and begins tracking connection health.
2. Resolving Multi-Factor Checkpoints Step-by-Step
When connecting your sender accounts, be prepared for three primary verification challenges:
Case A: SMS or Email OTP Verification
LinkedIn will send a 6-digit numeric verification code to your registered email address or phone number.
- The Solution: Wait 30 seconds for the code to arrive, type it directly into the OutFlo connection popup, and click Solve Checkpoint.
- Failed to Receive Code? Click the Resend Code link to trigger a fresh challenge. Avoid clicking this repeatedly as LinkedIn may lock the session for 24 hours.
Case B: 2FA App Verification (Google Authenticator)
If you have multi-factor authentication active on your LinkedIn account, it will ask for a timed verification token.
- The Solution: Open your Google Authenticator, Microsoft Authenticator, or Duo application, copy the current active code for LinkedIn, and paste it into the OutFlo solve block.
Case C: In-App Mobile Validation (Push Approvals)
This is LinkedIn's most secure check. Instead of sending a code, it asks you to approve the login from an existing device.
- The Solution: You will see a prompt in OutFlo stating: Please open the LinkedIn app on your phone and click "Yes, it's me".
- Action: Unlock your mobile phone, open the native LinkedIn mobile app, check notifications, click Yes, it's me, and approve the session. You do not need to enter any code. OutFlo’s background polling will automatically detect the approval and complete the setup.
3. Best-in-Class Auto-Assigned Residential Proxies
To keep your accounts completely safe and avoid triggering geographic security alarms, OutFlo handles proxy infrastructure automatically. You do not need to purchase, configure, or maintain custom proxies.
- Zero Configuration: Every time you connect a LinkedIn sender profile, OutFlo automatically provisions and assigns a premium residential proxy specifically matched to that account.
- Geographic Preservation: If your sender resides in London, our system routes their automation session through local UK-based residential IPs. This ensures LinkedIn sees natural browsing behavior from their home region, rather than a suspicious cloud data center.
- Rotational and Dedicated Stability: We utilize dedicated, clean IP addresses to maintain session persistence. This prevents the frequent "location-switching" triggers that cause LinkedIn to flag accounts.

