Select a page from the sidebar to get started.
Manual Tasks Tester
Get Next Task
Fetch the next available task from the queue.
Post Task Results
Submit results for a completed task.
Extension
Connect Extension
Connect the Tester Atlas browser extension to your account.
Issue Token for Extension (for manual connect)
Generate a refresh token for use with the browser extension. This token will have a longer expiration time.
Store this token securely. It will only be shown once.
Scraping Stats
Task Counts by Status
Downloads
Export Your Data
Download your data as an Excel file. Select the sheets to include:
Analytics
Score a Connection
Enter a connection's LinkedIn vanity name to calculate connection strength using AI.
Connection Scores
Ideal Customer Profile
Existing ICPs
AI Flows ⏱️
Flow Instances
Connections Graph
Connection Details
Paths to Company
Users
Tenants
Create Tenant (ONLY IN OUR DB FOR NOW!!!)
Existing Tenants
Targets
Companies
Drop companies CSV here
or click to browse
Connections
Drop connections CSV here
or click to browse
Prompts
Create Prompt
Existing Prompts
Workers
Worker Stats
User Last Activity
Side Kick
Trigger Joanna Path
Trigger Joanna path checking for a user's first-degree connection. Creates engagement + getSecondConnections tasks if shared work/study history is found.
Reset getSelfVanityName Task
Send the user's getSelfVanityName scraper task back to the pool (status pending, attempt counter reset). Only allowed when the user has exactly one scraper task and it is getSelfVanityName — otherwise the request is rejected.
Recompute Warmth
Warmth scores are automatically recomputed every 14 days for pairs with new data (engagement, profile changes, new connections). The 14-day cooldown exists because re-scan data trickles in over days — batching avoids recomputing on every small change separately.
Clicking this button triggers immediate recomputation for a tenant — bypassing the 14-day cooldown. Only pairs with actual data changes since their last scoring will be recomputed (pairs with no new data are skipped).
Handyman
Per-user debug heartbeat (source 2). Pick a user to see their extension status, recent heartbeat reports, and queue a debug command for the next heartbeat. Baseline session/tab logs are captured every ~5 minutes automatically.
Extension status
Request command
Rides the user's next heartbeat (~5 min). One runs at a time per user; extras queue and drain one per cycle.
Queued / recent commands
Heartbeat history
Latest report
Recommendations
Create Recommendation
⚠ 0 users stuck on periodicRecommendation
The auto-cycle will retry on its normal cadence — these rows clear themselves once a retry succeeds. Trigger ad-hoc to fill the gap for this week; rows already filled show a green ✓. If the same row reappears across cycles, the failure is structural and engineering should investigate.