Signal
Agent Interoperability Changes the Integration Work
The next integration challenge is preserving authority and business meaning as work moves between platforms. A working connector is only the starting point.
The September signal
Salesforce’s 15 September announcements with Google Cloud and AWS describe more ways for external interfaces and agents to access CRM capabilities. Their availability schedules are mixed: some functions are live; the Gemini federated connector remains a private preview, while cross-platform voice orchestration is planned for the autumn. These are vendor statements, not evidence that every customer can deploy every combination today.
The useful signal is the direction of travel. Business applications are being exposed as capabilities that can be invoked from elsewhere. That changes the object an integration team must govern: a request can now carry an intention to act, rather than simply a demand to read a record.
Transport does not settle meaning
Consider an illustrative request to close an opportunity and arrange fulfilment. The CRM may recognise a won deal, while finance requires a credit check and operations needs an accepted delivery date. A protocol can convey the request without resolving those differences.
The valuable design work is to define preconditions, permitted state changes and the system that owns each decision. A field mapping answers where a value goes. A business contract answers what the receiving system is entitled to do with it. Both are necessary, but only the latter explains whether the workflow is correct.
Delegation needs an unbroken record
For every consequential action, the receiving application should be able to distinguish the initiating person, the executing agent and the authority under which it acts. Shared service credentials can obscure that distinction. A platform recognising a user is not sufficient proof that a downstream action was authorised.
A practical acceptance test is to follow one request across its entire path. Can the team reconstruct what was requested, which policy was evaluated, what changed and who can reverse it? If the trace stops at a platform boundary, the integration is observable only in fragments.
Price the exception path
A successful demonstration usually follows the cleanest route. Production work also includes expired permissions, conflicting updates, unavailable systems and retries after an uncertain response. A repeated request must not silently create a second order. A partial completion must not appear as full success.
For an integrator, these conditions belong in the statement of work and acceptance criteria. Otherwise connector delivery looks complete while operational responsibility remains unresolved. The commercial opportunity is to make the cross-platform workflow supportable, including its failure behaviour and the evidence needed to investigate it.
What would confirm the shift?
Watch procurement requirements rather than partnership counts. Evidence of a meaningful shift would include buyers demanding shared action logs, explicit delegation rules, documented recovery behaviour and a named service owner across vendors. Also watch which announced capabilities reach general availability in the required region.
If implementations continue to require extensive custom mediation, open protocols will still be useful, but the reduction in integration effort may be smaller than the launch narrative suggests. The judgement should change with delivery evidence, not with the number of supported logos.