Upwork Automation Using Ai

# Upwork Automation Using AI

Workflow

1. Keep one active browser session/tab unless user explicitly asks to switch.
2. Open Upwork and ensure login state.
3. If logged out, run login automation:
4. - go to Upwork login page
5. - prefer "Continue with Google" when user asks for Gmail login
6. - fill email/password only from user-provided credentials for this run
7. - complete required next step (password, captcha/2FA/manual checkpoint)
8. - verify logged-in indicators before continuing
9. Collect/confirm criteria:
10. - allowed job types/stack
11. - minimum client quality thresholds
12. - disqualifiers
13. - proposal constraints (submit or draft-only)
14. Search jobs and shortlist visible matches.
15. Reject jobs with any disqualifier.
16. Pick the best remaining job (or top N if user asks).
17. Open job detail and click Apply.
18. Detect proposal location:
19. - if same tab, continue
20. - if new tab/window, switch to it (or ask user to activate once if tool cannot switch)
21. Fill proposal fields completely.
22. Stop before submission unless user explicitly says submit.

Hard Rules

• Do not submit proposal unless user explicitly says to submit now.
• Stay in the same tab/session unless user requests switching.
• After clicking Apply, immediately check whether proposal opened in same tab.
• If proposal opens in a new tab/window, auto-switch to that tab when the tool supports tab targeting.
• If auto-switch is not supported by the active tool, instruct user to activate the new tab once, then continue there.
• If a modal blocks actions, close modal first, then continue.
• Validate on-page state with screenshot/text checks before risky clicks.
• Never persist credentials to skill files or notes; use credentials only for the active run.

Job Filtering Rubric

Treat a job as valid only if all required checks pass.

• Required:
• Job type matches user scope (ecommerce stack or general development)
• Posted within time window (default <= 3 days unless user changes)
• Client quality meets thresholds (e.g., avg hourly >= $10 if visible)
• Fixed budget >= $100 when fixed-price budget is visible

• Disqualify when any is true:
• Individual-only hiring restriction
• Urgent/start-today pressure language
• No/poor payment history when user disallows it
• Requires screen share, onsite reporting, strict time tracking, or skill tests (if disallowed)

• If uncertain from visible data:
• mark as "needs manual review"
• do not claim it fully passed

Proposal Drafting Template

Use concise, specific structure:

1. Direct fit opening (stack + outcome)
2. Delivery plan (milestones/timeline)
3. Relevant proof (similar builds)
4. Communication cadence
5. Clear CTA

Prefer concrete numbers and short bullets over long paragraphs.

Execution Notes (Browser Reliability)

• Prefer deterministic selectors and verify each transition with screenshot/get_text.
• If generic selectors misfire, target by nearby unique text.
• If automation cannot switch to newly opened tab, ask user to bring proposal tab active and confirm.
• Keep browser open at end and report exact completion status:
• - job selected
• - proposal fields filled
• - submission state (not submitted)

Output Format to User

After completing work, respond with:

• Selected job: <title>
• Why selected: <criteria match summary>
• Fields filled: <key fields>
• Submission: Not submitted
• Next action: “Review and tell me ‘submit now’ if you want me to send it.”