Integration · Salesforce + Agentforce
Govern every Agentforce action
against AU + global regulators
MCP-based adapter that gates Agentforce actions against APRA, ASIC, OAIC, ISO 42001 and 13 more — running inside your Salesforce trust boundary, not someone else’s SaaS.
◐ In design partnership — shape it with us
What we’re building together
Adapter shape
- →MCP server (Model Context Protocol) hosted in your VPC. Agentforce calls it like any other context source.
- →Apex callable wrapper for Flow / Process Builder hooks, so non-Agentforce automations can also gate.
- →Decision row written to your DATAP.AI engine + optionally mirrored as a related-list record on the Salesforce object.
- →AppExchange managed package on the roadmap — post-pilot, post first AU regulator-citing demo.
Why this matters now
- ✓Agentforce ships fast — your CCO has no native way to enforce APRA / ASIC / OAIC across agent actions today.
- ✓Salesforce’s own Trust Layer is good for prompt safety; it’s not a regulator-mapped audit trail.
- ✓Customer-VPC deploy means data never crosses your perimeter — important for AFSL / APRA-regulated workloads.
- ✓Cited refusals appear inline in the agent response — “Based on APRA CPS 230 + OAIC APP 11…” — auditor-ready out of the box.
What design partners get
We work with 2–3 design partners per platform. You get influence on the integration shape, the data contract, and which regulator citations land first in Salesforce-originated audit rows. We get sharp customer feedback before we ship the AppExchange package.
Co-design sessions
Weekly working sessions on adapter shape + audit data contract.
Early access
Pilot key + customer-VPC deploy support before public availability.
Co-marketing
Joint case study + Salesforce ecosystem co-sell motion.