Session Objective

Close out the June 6 Marketing Center handoff where Salesforce OAuth reauth was the sole blocker preventing live Litify-backed dashboard refresh.

What Was Accomplished

• Confirmed LITIFY_ORG was connected and live SOQL reads worked from the Salesforce CLI.
• Fixed the Cloudflare Worker OAuth entrypoint so /oauth/start uses the Salesforce My Domain instead of login.salesforce.com.
• Updated Salesforce Connected App SamAguiar_AI_Integration to include the explicit Api OAuth scope while preserving Full, RefreshToken, the existing callback URL, and infinite refresh-token policy.
• Added a pragmatic Worker auth fallback: try refresh token first, then use the configured Salesforce username/password/security-token path if the refresh token is rejected.
• Verified direct Worker MCP calls for get_user_info and soql_query against litify_pm__Matter__c succeed.
• Patched the Marketing API SOQL fields in services/marketing-api/main.py and pushed commit d274b9f Fix Marketing API Litify segment SOQL.
• Triggered Render deployment for sail-marketing-api; deploy dep-d8llhq8jo6nc73bvg4cg for commit d274b9f reached live.

Verification Evidence

• sf org list showed LITIFY_ORG connected as sam@kylawoffice.com.
• sf data query --target-org LITIFY_ORG --query "SELECT Id, Name FROM litify_pm__Matter__c LIMIT 3" succeeded.
• curl -I <https://mcp.aguiarinjurylawyers.com/oauth/start> redirects to samaguiarinjurylawyers2.my.salesforce.com.
• Direct Worker MCP get_user_info returned user sam@kylawoffice.com.
• Direct Worker MCP soql_query returned a Matter row.
• python3 -m py_compile services/marketing-api/main.py passed before commit.
• curl -sS -X POST <https://sail-marketing-api.onrender.com/api/refresh> returned ok:true, an updated metric list, and errors:{}.
• curl -sS <https://sail-marketing-api.onrender.com/api/health> returned sf_mcp_live:true, litify_data_live:true, refresh_errors:{}, refresh_error_count:0, and stale:false.

Key Identifiers