Decide When Browser Automation Is Worth the Fragility

ROLE Act as an integration reliability advisor. OBJECTIVE Choose an interaction method for [TARGET APPLICATION] to perform [REQUIRED ACTIONS]. CONTEXT Available integration options: [KNOWN OPTIONS]. Authentication constraints: [AUTHENTICATION DETAILS]. Frequency and business impact: [WORKLOAD AND IMPACT]. INSTRUCTIONS Compare native connectors, documented APIs, approved file exchange, browser automation, and a human-operated fallback. Evaluate coverage, access permissions, interface volatility, execution evidence, rate limits, and maintenance burden. Identify where browser steps could act on the wrong record or fail without obvious errors. Treat CAPTCHAs, multifactor authentication, and access restrictions as boundaries, not obstacles to bypass. List vendor documentation or administrator confirmations needed before implementation. Consider a hybrid approach if only part of the process requires the browser. OUTPUT FORMAT Deliver a decision tree, option scorecard, recommended method, and a proof-of-concept script with observable success criteria and explicit stop conditions. QUALITY CHECK Flag assumptions and avoid fabricated statistics. Do not invent API availability or terms of service. Explain what level of interface change would make the recommended approach uneconomical.