Integrations & availability
Start with the work.
Verify the connection.
The right integration is the one that supports your actual client workflow. Confirm the account, operation, AI client and required controls before a pilot.
Current evidence
Availability, precisely stated.
Reviewed 13 September 2026. Code implementation, live validation and pilot availability are different stages.
| System | Implemented / tested | Live validation | Pilot scope |
|---|---|---|---|
| Google Ads | Read-only campaign performance: cost, clicks and impressions over supported fixed date ranges. | End-to-end read with a client-authorized credential bundle remains pending in the reviewed evidence. | Confirm account authorization, tenant-supplied credentials and the exact operation before agreeing scope. |
| MCP clients | Protocol interaction tested locally with the official MCP SDK. | No specific AI application or model provider is claimed as live-validated here. | Verify your selected AI client and authentication path together. |
| Additional connectors | No additional connector is represented here as supported. | No live-validation claim. | Discuss a requirement. New connector work needs a separate scope; no delivery date is promised. |
What a pilot proves
Evidence for your exact workflow.
Agree the client account, read or write permissions, allowed operations and expected workload. The console screenshots on this website show a demo workspace with sample clients, metrics and connector states. They do not establish live connector availability.
Verify the allowed request, a refused cross-client attempt, credential handling and the resulting audit record. Automated isolation tests are evidence of code behavior; they do not establish a deployed multi-client estate.
Availability depends on the connector and your client’s authorization. A scoped pilot lets both parties assess fit.
Review controls and evidence →