Overview
Connect your own LinkedIn account to CampaignStack, set up your workspace, and see meeting status inside your LinkedIn inbox.
CampaignStack runs B2B outreach from your own LinkedIn account. This extension is how the account gets connected, and how you can tell the connection is still working. - Creates your workspace from the toolbar. Click the icon and the extension reads who you are signed in as on LinkedIn, then offers to create your CampaignStack account and workspace. Nothing is created until you click the button. You get a command to paste into Claude or another AI client, and a field to claim the workspace with your email address so it stays yours. - Hands your LinkedIn session to CampaignStack when you click Import in the web app, so the campaigns you set up keep running. You never type a password here, and you never copy a cookie out of developer tools. - Checks every five minutes that the session still works, and tells you before a campaign stops rather than after. - Puts a small badge on a LinkedIn message thread when CampaignStack is arranging a meeting with that person, or has already booked one. The badge opens the briefing in your dashboard. It shows up on message threads and nowhere else. Getting started: install it while signed in to LinkedIn, click the toolbar icon, then enter your email address to claim the workspace.
0 out of 5No ratings
Details
- Version1.1.0
- UpdatedSeptember 19, 2026
- Size61.54KiB
- LanguagesEnglish
- DeveloperWebsite
Email
contact@campaignstack.io - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site