### What's the difference between a connector and an MCP server?

A connector (HubSpot, say) is the specific, lower-friction path for one concrete system: fill in a
credential and you're done. An MCP server is the generic path for any system that doesn't have a native
connector yet, with more configuration steps in exchange for covering practically any system you already
work with. See **[How they work](/en/integrations/)**.

### Does connecting an integration turn its actions on automatically?

No. Every action starts off — the same "nothing turns on by default" principle that governs your agents'
resources. Turn each one on individually, only the ones you need.

### Can the agent delete data on the external system?

No. The tools the agent uses in a conversation only search, create and update — never delete anything on
your external system.

### What if my industry doesn't have the integration I need enabled by default?

You'll see "Available on request" on its card, with a button to ask your provider — or, in the meantime,
the generic path of an MCP server stays open for that same system.

### Can I have more than one system of the same type connected at once (two CRMs, say)?

It depends on the specific integration — some only allow a single active connection per account at a
time; each connector's page in the **[catalog](/en/integrations/catalogo/)** says so.

### Where do I see whether an integration action failed?

Use "Test connection" on the integration's card to rule out a credential problem. If it persists, contact
Support.

### Can I connect a system that isn't in the catalog?

Yes, with an external MCP server (BYO-MCP), under your own responsibility — or request the specific
integration right from the Integrations screen.