Pipedrive CRM for nonprofits: why Notion isn’t a CRM
Need a nonprofit CRM with shared email visibility? See why Notion falls short without workarounds—and why Pipedrive is the simpler fit for small teams.
Claude Cowork Setup: Chrome Extension + Auth Workflow
Set up Claude Cowork with the Chrome extension, sign into Zapier and Shopify, choose the right model tier, and run supervised browser tasks reliably.
TABLE OF CONTENTS
Start Claude Cowork by installing Claude in Chrome, authenticating your apps, and running one supervised task end-to-end. Here's the repeatable setup that prevents the most common "it can't access X" errors.
What Claude Cowork is (and when to use it)
Claude Cowork is best when you want Claude to do the work inside a real browser session (clicking, navigating, editing, publishing) instead of only telling you the steps.
Use Cowork when you want outcomes like:
- Fix a broken Zapier Zap by checking the editor, validating filters, and publishing updates
- Upload a batch of products into Shopify by pulling images/specs from Dropbox and creating products in admin
- Run multi-tab troubleshooting (for example, reviewing failed Zap runs while a different task indexes a folder)
Prerequisites (do this once)
1) Install the Claude in Chrome extension
- Open Google Chrome (not Safari or another browser).
- Install the Claude extension from the Chrome Web Store.
- Pin it so it’s always visible (Puzzle piece → Pin next to Claude).
- Sign in to your Claude account inside the extension.
If Cowork says it can’t use Chrome yet, this is almost always the missing step.
2) Log into your web apps in Chrome first
Cowork can only work inside the authenticated browser session you already have.
Before you start a task, open these in Chrome and confirm you’re signed in:
- Zapier
- Shopify (admin)
- Dropbox (if the files live there)
If you can see the dashboard without a login prompt, Cowork usually can too.
The 10-minute “first run” workflow
Step 1: Start Cowork and confirm Chrome access
In Cowork, start a new task and ask something like:
- “Do you have access to my Chrome browser? If not, what do I need to enable?”
If it’s connected, you’ll typically see it open a Chrome tab group and you’ll notice the cursor moving with a highlight.
Step 2: Give the task goal (one sentence) + the success criteria
Cowork works best when you set the finish line clearly.
Examples:
- “Fix the broken abandoned cart Zap and publish the updated Zap. Then tell me whether I should rerun failed runs and what risks exist.”
- “Create a new Shopify product for each image in this Dropbox folder URL, using my existing feather flag product as the template for description/tone.”
Step 3: Provide the key resource link(s)
If files live in Dropbox, paste the exact folder URL.
If the task is about an error, paste the exact Zap link or open it in a tab so Cowork can find it.
Step 4: Let Cowork ask questions (don’t over-instruct)
A strong operating model:
- Claude indexes what it can see (tabs, folders, settings)
- Claude asks clarifying questions
- You answer quickly and approve the plan
- Claude executes with supervision
This saves tokens and reduces backtracking.
Recommended permission settings (and when to use them)
Cowork will often ask for permission to use a site.
- Use “allow” for the specific site when you’re testing
- Use broader permissions (like “allow all browser actions”) only when you’re confident the task is correct and you want it to move faster
If you’re just learning, keep it in “ask” mode until you’ve seen a few successful runs.
Choosing the right model tier (cost vs capability)
If you’re running into usage limits or you don’t need deep reasoning, step down the model tier.
A simple rule:
- Use a higher tier when the task needs real troubleshooting, judgment, or multi-step reasoning
- Use a lower-cost tier when the task is mostly “click here, copy that, create items from a list”
Also note: you generally can’t change the model once a Cowork session starts, so choose before you hit “go.”
Two high-signal examples you can copy
Example A: Fix a broken Zapier Zap
Prompt:
- “Open Zapier in Chrome, find the broken abandoned cart Zap, identify the failing step, apply the recommended fix, and publish. After publishing, review the failed run history and tell me whether rerunning failed runs could double-send emails or create duplicate orders.”
Example B: Bulk product creation in Shopify (from Dropbox)
Prompt:
- “I’m logged into Shopify admin in Chrome and logged into Dropbox in Chrome. Here’s the parent folder URL: (paste). Create one Shopify product per image, group them into the correct collection, and base the description on my existing ‘Custom Feather Flag’ product. Ask questions before you start creating products.”
Troubleshooting: common setup failures
- Cowork can’t access your app: open it in Chrome and log in first.
- It keeps asking for the same permission: verify the extension is installed, pinned, and signed in.
- Zapier warns about multiple tabs open: close duplicates before Cowork edits.
- The desktop app says “relaunch to update”: do that before starting new tasks (relaunching mid-task can interrupt the run).
Get help building reliable browser automation
If you want Cowork to run repeatable, reliable work (without babysitting every click), you'll need the right guardrails, app permissions, and automation architecture behind it. Connex can help you scope the workflow, set the right permission model, and connect Claude Cowork to the rest of your stack.
Related Posts
Notion database for teen group therapy attendance + notes
Build a Notion system to track teen group therapy attendance and session notes with relational databases, rollups, and simple Make automations for parent emails.
How an AI Voice Agent Replaced 90+ Weekly Confirmation Calls
Learn how a market research firm automated 90+ weekly confirmation calls with an AI voice agent built on Twilio, 11 Labs, and Zapier. See the exact architecture.
