Claude Cowork Scheduled Task Automates Browser-Based Admin Work: A Real Use Case

A Reddit user shares how they automated a repetitive browser-based admin workflow using Claude Cowork's scheduled tasks and Chrome extension. The task: processing publisher applications across five affiliate network accounts, each receiving 10–15 applications per week.

Before vs. After

Previously: email notifications for each application, manual login every few days, manual accept/reject based on criteria. Now: a scheduled Cowork session runs once a week (Wednesday mornings) and autonomously handles applications across all five accounts.

Implementation Details

The user kept scheduled task instructions brief and placed detailed logic in a skill that the task loads, making updates easier. The skill instructs the task to use the Chrome extension to navigate to each account's publisher application page.

Critical Manual Step

The workflow includes a rule: if the affiliate network's login page is hit, the task waits for manual login. The browser extension cannot fill login forms. The user reports this takes ~5 seconds per session, and the task waits instead of aborting. Key instruction: "wait for the user to log in".

Autonomous Workflow

Once logged in, the task runs 100% autonomously, applying acceptance/rejection criteria defined in the skill:

• Publisher type (e.g., reject all coupon sites)
• Industry focus (e.g., always accept automotive)
• Application language and content
• Criteria vary slightly per account

Result

The automation saves significant time weekly and eliminates email noise. The user now trusts the weekly scheduled task and briefly scans the report generated after each run.

Key Takeaway

For repetitive browser work without API support, Claude Cowork + Chrome extension can fill the gap. The skill-based instruction pattern makes it easy to iterate on logic without touching the scheduled task configuration.