Choosing a connection method

Updated 25 September 2026

Overview

When you add an account for Amazon Bedrock, Microsoft Copilot, Salesforce, or Snowflake Cortex, the first step asks how Agent Control Tower should receive that account's data. Your answer determines whether you get metrics for those agents, so make it deliberately.

Choose Boomi Sync to have Boomi pull agent metadata for you. You supply the provider's credentials and Agent Control Tower connects to the provider and pulls in all the agents present on that account. However, Microsoft Copilot, Salesforce, and Snowflake Cortex return no metrics using this way.
Choose API Push to send metadata and metrics yourself. This is the only way to get metrics for Copilot, Salesforce, and Snowflake Cortex, and it is also how you connect any provider that Agent Control Tower does not support natively. Boomi Agent Garden and Anthropic Claude Managed Agents do not offer this choice. They connect natively and report metrics without any additional configuration.

Prerequisites

An account with Amazon Bedrock, Microsoft Copilot, Salesforce, or Snowflake Cortex.
For Boomi Sync: the credentials that provider requires. These differ per provider:
For API Push: a system that can send agent metadata and metrics to Agent Control Tower. For more information, refer to Custom provider accounts API.

Key concepts

Boomi Sync: Boomi pulls metadata automatically. Amazon Bedrock, Boomi Agent Garden and Anthropic Claude Managed Agents reports metrics through this method. Microsoft Copilot, Salesforce, and Snowflake Cortex do not.

API Push: You push metadata and metrics through the API. Metric coverage depends on what that provider's API exposes.

Choosing a connection method

You choose the connection method while adding a provider account.

Go to Provider Accounts.
Start adding an account. You can either:
- Click Add Account on the provider's tile, or
- Click Connect to different provider and select the provider.
The Connect {Provider} Account panel opens at Step 1: How do you want to connect?
Select Boomi Sync or API Push.
Complete the remaining steps in the panel. The fields you see depend on the provider and the method you chose.

For the provider-specific steps that follow if using Boomi Sync, refer to that provider's page.

Comparing the two methods

	Boomi Sync	API Push
Who moves the data	Boomi pulls it	You push it
Setup required	Provider credentials only	An integration that sends to the API
Agent metadata	Yes, synced automatically	Yes, whatever you send
Metrics	Boomi Agent Garden, Anthropic Managed Agents and Amazon Bedrock only	For metrics they need to use Monitoring specification- present in “Deployed agent” and do the setup to push the metrics.
Keeping data current	Automatic	Your responsibility

Agent Control Tower provider capabilities

What Agent Control Tower can show you depends on both the provider and the connection method. Use the tables below to check a specific combination before you connect.

Providers connected using Boomi Sync

Boomi Sync catalogs a provider's agents and syncs their metadata automatically, with no setup beyond supplying credentials. Most providers poll every 30 minutes, though the cadence varies (see note ² below).

Boomi Sync does not surface every piece of data a provider holds, and for Copilot, Salesforce, and Snowflake Cortex it returns no metrics at all. To get metrics from those providers, connect them using API Push instead.

Legend: ✓ available, ✗ not available, n/a provider does not expose this concept.

Capability	Agent Garden	Bedrock	Copilot	Salesforce	Cortex	Anthropic Claude
Agent metadata
Agent status	✓	✓	✓	✓	✓	✓
Agent description	✓	✓	✓	✓	✓	✓
Version¹	✓	✓	✓	✓	✗	✓
Tools	✓	✓	✓	n/a	✓	✓
Instructions	n/a	✓	✓	n/a	✓	✓
Knowledge Base	✓	✓	n/a	n/a	n/a	n/a
Glossaries	✓	n/a	n/a	n/a	n/a	n/a
Guardrails	✓	✓	n/a	n/a	n/a	n/a
Management
Enable / disable agent	✓	✓	✗	✓	✗	✗
Auto-sync	✓ (30 min)	✓ (30 min)	✓ (30 min)	✓ (30 min)	✓ (30 min)	✓ (event-driven)²
Tags and trust levels	✓	✓	✓	✓	✓	✓
Monitoring and metrics
Invocations	✓	✓	✗	✗	✗	✓
Average time per invocation	✓	✓	✗	✗	✗	✓
Token usage (input / output)	✓	✓	✗	✗	✗	✓
Errors	✓	✓	✗	✗	✗	✓³
Session logs / tracing	✓	✗	✗	✗	✗	✗
Anomaly detection	✓	✓	✗	✗	✗	✗
Activity logs	✓	✓	✓	✓	✓	✓

¹ Agent Control Tower registers each Bedrock agent version and alias as a separate agent entry.

² Anthropic Claude Managed Agents sync via webhook-driven agent and session lifecycle events rather than a fixed poll — changes typically reach Agent Control Tower within minutes of occurring in the Anthropic Console. For details, refer to Anthropic Claude Managed Agents.

³ "Errors" for Anthropic currently appears to cover model-invocation errors only, not agent-invocation-level server/client errors

Providers connected using API Push

API Push lets you bring any agent into Agent Control Tower, including agents from a natively supported provider. Nothing syncs automatically. You add and maintain the agent's metadata yourself, manually or through the API, so keeping it accurate is your responsibility.

To report metrics, the provider must expose usage data you can map to the Agent Control Tower metrics endpoint. You push that data through the Custom Provider APIs, and Agent Control Tower displays what it receives. For more information, refer to Enabling metrics of Custom accounts.

Capability	API Push
Agent metadata (status, description, version, tools, guardrails)	Supported. You add and maintain these values manually, via API, or via AI catalog. There is no live sync, so keeping them current is your responsibility.
Enable / disable agent	Not available
Auto-sync	Not available
Tags and trust levels	Supported
Metrics (invocations, average time, token usage, errors, throttles, tool usage)	Supported. You implement the metric mapping using the Custom Provider monitoring specs and push metrics through the Custom Provider APIs. Agent Control Tower displays what it receives.
Session logs / tracing	Not available
Anomaly detection	Supported, calculated from the metrics you push
Activity logs	Supported