Question 1

What is Weavz?

Accepted Answer

Weavz is an integration infrastructure platform (embedded iPaaS) that provides connection management, MCP servers, triggers, and action execution for third-party services. It lets you add integrations to your product without building them from scratch.

Question 2

What is MCP?

Accepted Answer

MCP (Model Context Protocol) is an open standard for AI agents to discover and use tools. Weavz exposes your integrations as MCP tools, so AI agents can automatically find and call them. Think of it as a universal plugin system for AI.

Question 3

How many integrations are available?

Accepted Answer

Weavz currently supports 500+ integrations with 3,600+ tools (actions + triggers), including Slack, Google Sheets, Gmail, GitHub, Notion, HubSpot, Salesforce, and more. New integrations are added regularly. You can also use the HTTP integration to connect to any REST API. Need something custom? We ship custom integrations in under 17 hours.

Question 4

Is Weavz open source?

Accepted Answer

Weavz is a proprietary platform available as a managed SaaS service with global edge delivery. For private cloud deployments or custom requirements, contact our sales team.

Question 5

What is the difference between TOOLS and CODE mode?

Accepted Answer

TOOLS mode exposes each integration action as a separate MCP tool with full JSON Schema — standard but context-heavy (200+ tools). CODE mode replaces all tools with 3 meta-tools (weavz_search, weavz_read_api, weavz_execute) that let AI agents explore APIs on demand and write code, reducing context by 80-98%.

Question 6

How are credentials stored?

Accepted Answer

All credentials are encrypted at rest using AES-256 with a per-environment encryption key. Credentials are scoped to org + workspace and never exposed in API responses. OAuth2 tokens are automatically refreshed when they expire.

Question 7

What runtime does Weavz use?

Accepted Answer

Weavz runs on global edge infrastructure with auto-scaling and zero cold starts. A flexible architecture keeps the platform adaptable. For enterprise customers needing private cloud deployments, contact our sales team.

Question 8

How does code execution work?

Accepted Answer

Code Mode executes JavaScript in a sandboxed environment. A lightweight sandbox provides fast, in-process execution with sub-millisecond startup. For full runtime needs, a full sandbox environment offers complete runtime access with filesystem and networking. Both support persistent storage via the Storage integration.

Question 9

Can I use Weavz without MCP?

Accepted Answer

Absolutely. Weavz provides a full REST API for executing actions, managing connections, and controlling triggers. Use Bearer token authentication (wvz_ prefix) to call any endpoint from any language. TypeScript and Python SDKs are also available.

Question 10

What are End Users?

Accepted Answer

End Users represent the people using your product. Weavz provides a unified identity system where each end user can connect their own accounts, manage connections through a self-service portal, and have their own scoped MCP servers. You can create end users via the API/SDK or invite them via email.

Question 11

What is Hosted Connect?

Accepted Answer

Hosted Connect is a pre-built connection flow that handles all authentication types (OAuth2, API keys, custom auth) in a popup window. Generate a connect token via the API, open the hosted page, and your user completes authentication — no need to build your own auth UI.

Question 12

What are Input Partials?

Accepted Answer

Input Partials are saved parameter presets scoped to a workspace. They let you pre-fill or enforce specific values for actions — for example, always sending Slack messages to a specific channel. Enforced values cannot be overridden at runtime, giving you control over how actions are used.

Question 13

What are Workspace Integrations?

Accepted Answer

Workspace Integrations let you configure which integrations are available in a workspace, each with an alias, connection strategy (fixed, per_user, or per_user_with_fallback), and optional action whitelist. MCP servers can sync their tools from a workspace to automatically inherit this configuration.

Question 14

What is API Key Scoping?

Accepted Answer

API keys can be scoped to specific workspaces for least-privilege access control. Org-wide keys have full access, while workspace-scoped keys can only access resources within their assigned workspaces. This lets you give your backend services only the access they need.

Question 15

Is there a free plan?

Accepted Answer

Yes. The Free plan includes 1,000 actions per month, 5 connections, 25 MCP servers, and community support. No credit card required.

Question 16

What counts as an action?

Accepted Answer

An action is a single API call to a third-party service — for example, sending a Slack message, appending a Google Sheets row, or creating a GitHub issue. Weavz_search and weavz_read_api calls in Code Mode do not count as actions.

Question 17

Can I purchase additional actions?

Accepted Answer

Yes. Action add-on packs are available: 10K ($5), 50K ($15), 200K ($40), and 1M ($100). They stack on top of your plan's monthly quota and can be purchased anytime from the billing dashboard.

Question 18

What happens when I hit my action limit?

Accepted Answer

You'll receive a clear error response with a QUOTA_EXCEEDED code. Existing triggers and MCP servers continue to function — only new action executions are blocked. You can upgrade your plan or purchase an add-on pack to resume immediately.

Question 19

How do resource overages work?

Accepted Answer

On paid plans, you're never hard-blocked from creating resources. Additional connections, workspaces, and MCP servers are $0.10/mo each. Additional team members are $5/mo each. You can set an optional spend cap to control overage costs.

Question 20

Are there sandbox and storage add-ons?

Accepted Answer

Yes. Sandbox packs (+10hr/$15, +50hr/$50), storage packs (+5GB/$5, +25GB/$15), and KV store packs (+10K/$5, +100K/$15) are available on all paid plans. They apply immediately to your current billing period.

Question 21

Is my data encrypted?

Accepted Answer

Yes. All credentials and sensitive configuration are encrypted at rest using AES-256. Data in transit is encrypted via TLS. The encryption key is set via environment variable and never stored in the database.

Question 22

Can I run Weavz on my own infrastructure?

Accepted Answer

On-site and bring-your-own-cloud (BYOC) deployments are available for Enterprise customers. Contact our sales team at /contact to discuss your requirements, including custom SLAs, data residency, and dedicated infrastructure.

Question 23

Does Weavz store my users' data?

Accepted Answer

Weavz stores encrypted credentials and action execution logs (configurable retention: 7-365 days by plan). Action inputs and outputs are logged for debugging but can be disabled. No user data is shared with third parties.

Frequently Asked Questions

General

Technical

Pricing

Security

Still have questions?