Connect services once, then use them where they help—ASK CONE, BUILD, TODAY, LEARN and more. CONE only shows integrations as connected when the server confirms they are configured.
One connection. Useful everywhere.
When supported, CONE can use approved capabilities across relevant workflows. Sending messages, publishing, deleting files, or spending money should require explicit approval. Planned integrations are labeled honestly; no fake connected states.
Loading current integration status…
No tools match those filters.
What happens next?
A listing is not a working connector: each one has to be signed in with its official API, tried and checked before CONE calls it connected.
Review each integration's permissions and setup. For services marked “not connected,” CONE explains what's missing rather than pretending it has access.