Connect it to
everything you already run
Messaging channels, HTTP APIs, databases, MCP servers and sandboxed code — described rather than coded, so an agent can reach the system that holds the answer instead of apologising for not knowing.
Six ways to reach the rest of your stack
Whatever the system is, one of these already covers it.
Any API, described not coded
Give a tool an endpoint, a method, an auth header and its parameters, and your agents can call it. Import an OpenAPI spec and the operations arrive already described.
Code when describing is harder
Python or JavaScript in a sandbox, callable as a tool. For the reshaping, parsing and arithmetic that is faster to write than to explain to a model.
MCP, both directions
Connect your agents to any MCP server and discover its tools at runtime — and drive this workspace from an external MCP client, including a coding agent building your agents for you.
Agents as tools
Expose one agent to another. A supervisor delegates to a specialist and gets a structured answer back, instead of a second copy of the specialist inside its own prompt.
Channels as integrations
Messenger, Zalo, Telegram, Pancake and a website widget connect as first-class channels. Anything else arrives through the Custom API channel — a webhook in, a webhook out.
See the AI inboxEvents pushed to you
Inbox events reach endpoints you own, so a new message can trigger something in your stack. Delivery is logged, so a receiver that was down is visible rather than lost.
The catalogue
What connects today, by kind.
Messaging channels
- Facebook Messenger, and comments with private reply
- Zalo Official Account and personal Zalo
- Telegram bots
- Pancake accounts
- Website chat widget
- Custom API — webhook in, webhook out
Tool types
- Built-in platform tools
- Webhook tools — any HTTP API, with bearer or key auth
- OpenAPI import
- Sandboxed Python and JavaScript
- MCP servers, discovered at runtime
- Agent-as-tool delegation
Data connections
- PostgreSQL, MySQL, SQL Server, Oracle
- BigQuery, Snowflake, Redshift, Databricks
- ClickHouse, DuckDB, SQLite
- Athena, Trino / Presto, Spark SQL
Publishing and services
- Facebook Pages and WordPress publishing
- Custom webhook destinations
- Connected app accounts for third-party services
- Shipping and logistics providers
- Transactional email
Programmatic access
- Workspace API keys, scoped to their creator’s permissions
- An MCP endpoint authenticated by the same key
- Outbound webhooks on inbox events
- Per-call logging with cost
Ready to install
- A marketplace of agent templates
- Templates cloned into your workspace, then edited
- Skills and tools shared across every agent
- Apps built on the platform and installed into a workspace
Integration questions
What engineers ask before wiring this into an internal system.
With a webhook tool. You describe the endpoint, the method, the auth header and the parameters, and the agent can call it — no code deployed on our side and none on yours beyond the endpoint you already have. If the service publishes an OpenAPI spec, import that instead and the operations arrive already described.
Yes — Python or JavaScript, in a sandbox, as a tool an agent can call. It is the right answer for the transformations that are easier to write than to describe: reshaping a payload, doing arithmetic a model should not be trusted with, parsing something awkward.
In both directions. Your agents can connect to any MCP server and discover its tools at runtime, and the platform exposes its own MCP server so an external client — including a coding agent — can drive your workspace: create agents, edit documents, query boards, manage skills and tools.
Yes. An agent can be exposed as a tool, so a supervisor can delegate to a specialist and get a structured answer back rather than reimplementing what the specialist already does.
Inbox events can be pushed to endpoints you own, so a new message or a resolved conversation can trigger something in your own stack. Delivery is logged, so a receiver that was down is visible rather than a message you never knew about.
Yes. API keys are issued per workspace and carry the permissions of the member who created them, so a key cannot do more than the person behind it. The same key authenticates the MCP endpoint.
Wire it into the system that has the answer
Describe an endpoint, connect a database, or point it at an MCP server. Free to start, no credit card.