Custom Integrations

Not every provider you use is already available as a category. GTM Goat connects new integrations as long as they bring a valid API or a valid MCP — that’s the only quality bar, there’s no exception for “some script”.

Quality bar

A new integration needs: a documented, stable API or an MCP interface, authentication that can be stored isolated per workspace, and behavior that maps to one of the existing categories (or justifies a new one). Loose scripts or providers without a robust interface don’t get connected — that would be exactly the toolchain fragmentation GTM Goat avoids.

Your own keys or platform access

For some categories (research and enrichment in particular) you can supply your own API key (BYOK) instead of using the platform-provided access — costs then run directly through your provider instead of your credit balance. Both are selectable per integration.

Self-service connection by the agent

Status: In development (staged rollout)

Eventually, Command will walk you through a new connection yourself: you name the API or the MCP, the agent reads the interface, proposes a mapping to fields and actions, and after your approval the integration goes live — no platform deploy. Today the cegtec team handles connecting new categories; self-service, workspace-side connection for any category is rolling out in stages.

See also: Categories for the integration categories already available.