Charms that connect to external tools. External tools that connect to CharmIQ. One consistent model for all of it.
|
|
Your Charms don't have to stay inside CharmIQ. They can reach out to the tools your work already runs on — and those tools can reach back in.
Two Directions, One Model
CharmIQ Integrations work in both directions:Outbound: Your Charms connect to external services. A Charm that can query your Google BigQuery data, trigger Zapier automations, browse your GitHub repositories or pull directly from Google's documentation. You authorize the connection once; the Charm uses it every time.Inbound: External tools connect to CharmIQ. Claude Code, VS Code, Zapier or a custom application can talk directly to your workspaces — running completions with your Charms, reading and writing documents, launching tasks.Inside your Applications: Custom Applications you build in CharmIQ can authenticate with external APIs with your consent. A dashboard that reads your Google Analytics data. An application that connects to the GitHub API. The same OAuth infrastructure that powers Charms also powers your custom tools.All three directions share the same underlying model: every connection requires explicit authorization, tokens are encrypted and managed automatically and you stay in control of what can access what.
The Mental Model
Think of it as a permission system with three parties:
The Charm or tool that wants to do something
The service it wants to access
You — who explicitly authorizes that relationship
Nothing connects automatically. You grant access; you can revoke it at any time. If you're on a Company plan then your Company administrator controls which services are available to connect to and what those connections are permitted to do.
What This Makes Possible
The real value is composability. A Charm with access to Zapier has potential access to thousands of services through a single connection. A Charm that can query BigQuery can analyze your actual data — not a summary someone pasted into a document. A Charm that can read your GitHub can answer "what shipped this sprint?" with real pull requests, not generative guesses.And because CharmIQ also accepts inbound connections, the same workspace your Charms work in is accessible from your terminal, your IDE or any MCP-compatible tool.