Concepts
Product primitives and mental models for building with Weavz.
Concepts
Use these pages to understand the Weavz object model before wiring API calls or SDK code. The same primitives appear in the dashboard, REST API, TypeScript SDK, Python SDK, MCP servers, and LLM resources.
Start Here
| Page | Use it for |
|---|---|
| Organizations & Workspaces | Resource hierarchy, workspace isolation, and tenant patterns |
| Identifier Model | The difference between Weavz UUIDs, your user IDs, connection external IDs, and namespace keys |
| Integrations | Catalog integrations, actions, triggers, and authentication types |
| Integration Selectors | integrationName, alias, integrationAlias, and workspaceIntegrationId |
| Connections | Credential ownership, hosted connect, and connection resolution |
| End Users | Per-user identity, connect portals, and per-user connection strategies |
Execution And Agent Surfaces
| Page | Use it for |
|---|---|
| Actions | Running third-party operations through REST, SDKs, Playground, and MCP |
| Triggers | Receiving external events through callback URLs |
| MCP Servers | Exposing workspace integrations to AI clients |
| Input Partials | Defaults and enforced values for actions, triggers, and MCP tools |
| Storage & KV Store | Built-in scoped file and key-value persistence |
| Code & Sandbox | Built-in code execution surfaces |
Operating Model
| Page | Use it for |
|---|---|
| Built-In Workspace Integrations | First-party tools such as Storage, KV, HTTP, Web Reader, and Advanced Code |
| Plan Limits & Quotas | Rate limits, resource caps, add-ons, and prepaid capacity |
Canonical Build Order
- Create or choose a workspace.
- Add workspace integrations with stable aliases and connection strategies.
- Add connections and end users.
- Add input partials and Human Gates for guardrails.
- Create MCP servers or execute actions and triggers from your app.
- Validate the full setup in Playground.