Skip to content
Weavz
Menu

Start here

Connect apps to your own AI, or embed app access in the product you build. Choose the Weavz path that matches your work.

Weavz connects AI agents to the apps people use for work. Connect accounts, let an agent read or act through those accounts, and keep a record of what happened.

Connect your own AI

Use Claude, ChatGPT, Codex, Cursor or another compatible MCP client with your own Gmail, Slack, Notion and other apps.

  1. Choose your AI client and add Weavz.
  2. Sign in and choose a workspace if you have more than one.
  3. Connect the app accounts you want to use.
  4. Ask your AI for a first task, such as summarizing an email thread or finding an issue.

You can do this without an API key or writing code. Read Connect your own AI for setup, account switching and recovery.

Build app access into your product

Let your customers connect their accounts to an agent or workflow you build. Your backend uses the Weavz API or SDKs to create connection links and execute actions for the right end user.

  1. Run the quick start.
  2. Connect a customer's account.
  3. Call actions through the API or give your agent MCP tools.
  4. Add events and triggers when your product needs to react to changes.

The AI product guide covers the complete customer connection and execution flow. Keep customer API keys on your trusted backend.

The concepts you need first

ConceptWhat it means
App integrationThe actions and events Weavz supports for an app, such as Gmail or Slack.
ConnectionAn authorized account that an action uses.
WorkspaceA set of apps, connections and tools for a particular project or use.
ActionA specific operation, such as reading a file or sending a message.
End userThe person in your product whose account an action should use. Personal connector sign-in establishes this identity for you.
MCPThe protocol a compatible AI client uses to discover and call tools.

A workspace can use multiple accounts from the same app. An alias gives each configured app a clear name, such as support_slack. Product builders can choose whether an app uses each end user's account or a deliberately shared account.

Optional controls

New workspaces start with all app actions available and no saved inputs. Connecting an account still requires its owner's authorization. Workspace boundaries, end-user identity and app permissions always apply.

  • Approval rules pause matching actions for a reviewer. Add a rule when you want your agent to ask before an action, such as sending a message. See approval rules.
  • Saved inputs reuse values for an action. For example, save a destination channel so an agent does not have to choose it each time. Locked values and automatic defaults are advanced options. See saved inputs.
  • Files, state and Sandbox support work that needs persistent outputs, checkpoints or code execution.

Find optional controls under Advanced in the dashboard. Existing rules and saved inputs keep their behavior. The API names approval-policies and partials remain supported.

Choose a useful first task

Templates show the apps, example request and setup for research, customer follow-up, support, engineering and daily work. They prepare tools for your agent; they do not start an autonomous agent or a schedule.

Start with client setup for personal use, or the developer platform for product embedding. Both use the same plans and included capacity.