$ Credential Flow

A live Salesforce integration built for this portfolio: a custom Loan_Application__c object model (Applicant → Loan Application → Account) in a free Salesforce Developer Edition org, called from this site’s own FastAPI backend via the OAuth 2.0 Client Credentials Flow. The list and create actions below hit the real Salesforce REST API against real records — this isn’t mocked data. See Architecture for the token lifecycle and full endpoint surface.

The API talks to Salesforce using raw httpx rather than the simple-salesforcewrapper, and OAuth 2.0’s Client Credentials Flow rather than a user-interactive flow — a server-to-server integration where no user is in the loop. See Design Notes for the full reasoning behind choosing raw httpx over a wrapper library.

This integration deliberately does not use Salesforce Financial Services Cloud or Agentforce — both require paid licenses that aren’t available in a free Developer Edition org. What’s built here is the closest honest approximation on standard objects: a custom object with lookups to standard Contact and Account, a Status picklist, and a Record-Triggered Flow that auto-stamps a decision date when status changes to Approved or Denied. It’s a simplified relationship model, not a claim of parity with a production FSC implementation.

The Applicant → Loan Application → Account relationship model here is structurally the same shape as Farpost’s own professional-reputation graphⓘ — entities linked through records that carry status and a decision trail. See Object Model for the full field list and the parallel in more depth.

Loading live data from Salesforce…

Three more read-only additions, chosen to speak directly to this role’s actual priorities rather than to be generically impressive. Select an Account below to see its Loan Applications grouped together — a small, concrete instance of relationship-centric data modeling, not just an implied lookup. Each application also offers an AI-generated “recommended next action,” produced by calling the Anthropic API directly — not Salesforce Agentforce, which isn’t licensed on this Developer Edition org, so this is an honest analog rather than a claim of using a product Robin doesn’t have access to. And each application’s status history is sourced from Salesforce’s own Field History Tracking — real audit-trail entries, not a fabricated summary from two date fields. Same principle as Farpost’s professional-reputation graph above: computed from actual events, not a stored score.