I automated the publisher application approval and rejection process across five affiliate network accounts I manage. Before, every account received 10 to 15 applications per week, and I manually logged in every few days to approve or reject them. Now a scheduled Cowork session runs once a week, uses the Chrome extension, follows account-specific criteria, and creates a report after every run. If it reaches a login page, it waits for me to log in instead of aborting.
⚙️ Automation Reddit
Weekly Publisher Application Approvals Across 5 Affiliate Accounts
Use Cowork scheduled tasks and the Chrome extension to handle an admin workflow with no API: approve or reject applications by account-specific criteria, wait for manual login when needed, and produce a run report.
★★★ Advanced 30-60 min setup, weekly scheduled run May 1, 2026
R
rebelytics
@u/rebelytics
Runs affiliate-network operations and uses scheduled Cowork browser tasks
📋
Scenario
The author manages five affiliate-network accounts. Each receives 10-15 publisher applications per week, and the only review path is a browser UI with no API.
💬
Prompt
Every Wednesday morning, open the affiliate network admin pages for all five accounts. If a login page appears, pause and ask me to log in manually. Once authenticated, review all open publisher applications. Apply the acceptance and rejection criteria from affiliate-approval-skill.md, including publisher type, industry focus, language, and account-specific rules. Approve or reject each application, then save a short report listing decisions, edge cases, and anything I should review.
✨
Expected Result
Cowork now opens all five account dashboards weekly and reviews applications using the criteria in a skill file. The only manual step is logging in when required. The author no longer keeps email notifications as reminders and only scans the report after each run.