Integrations
What CallingYou.AI connects to, how each connection works, and exactly how far along it is. Nothing here is live for customers yet — we would rather publish the map than imply partnerships we do not have.
Your CallingYou.AI calendar syncs with this provider over OAuth where the provider supports it, and over CalDAV credentials where it does not. Anything that writes into that calendar — a booking tool, a shared team agenda, a personal phone — becomes busy time the assistant respects, so we do not need a connector per business tool. The sync is in development and not available to customers yet.
Our calendar is a CalDAV server, so this client connects to it directly with a URL and credentials and there is no connector for us to build. You read and edit exactly the same appointments the voice assistant books. The server is in development and open to pilot accounts only.
This platform documents a public API, so we can build the connector ourselves without asking anyone for permission. The planned work is reading availability and writing appointments back into the platform. Nothing is implemented today and we are not affiliated with the vendor.
This platform exposes its API only through a partner or marketplace program, so a direct connector needs an agreement we do not have. Until then the calendar bridge is the honest path: whatever the platform syncs into a calendar we support, the assistant already sees. We list it here to be explicit about what is blocked and why.
Escalations and follow-ups leave the call as tickets through an MCP connector that runs on credentials your tenant provides, limited by an allowlist of the actions it may perform. You hold the credentials and can revoke them at any time. The connectors are planned; ClickUp is first in line.
All product names, brands and trademarks belong to their respective owners. They are used here for identification only and imply no partnership, endorsement or affiliation.
