Skip to content
Weavz
Menu

Your customers connect their apps. Your product does the work.

Add app connections to your product without turning every new workflow into a separate credential and integration project.

Weavz gives your backend a consistent way to connect accounts, execute app actions and receive events. Your product keeps the customer relationship and interface. Use workspace aliases to describe an app’s purpose, and choose whether credentials belong to an individual end user or an explicitly shared workspace.

Ship an integration people can actually use.

The API call is one part of the experience. Account selection, identity and recovery matter just as much.

Connect inside the customer journey

Create a Hosted Connect session from your backend and open the connection flow from your product. Explain which app the customer is connecting and what the resulting workflow will be able to do.

Execute typed app actions

Use the TypeScript or Python SDK to call a supported integration action. Supply the customer’s end-user identity and workspace alias so the action resolves the connection intended for that workflow.

React to app events

Configure supported triggers and deliver events to your application. Use event identity and processing state to keep your own handlers retry-safe. Trigger availability and provider setup vary by integration.

Give the integration a complete lifecycle.

  1. Step 1

    Map your product’s identities

    Choose a workspace boundary and create end users for your customers. Keep the mapping in your backend. Use a workspace-scoped API key when that is the appropriate access boundary.

  2. Step 2

    Configure the app once

    Add an integration alias, select enabled actions and choose a connection strategy. Generate a Hosted Connect link for the current end user instead of passing your Weavz API key to the browser.

  3. Step 3

    Handle the outcome in your product

    Execute the action or process the trigger. Show success from a confirmed result, explain reconnect or approval states, and keep a clear route back to the source record when a customer needs to investigate.

Design for the account that disconnected.

A production integration needs a clear way forward when access or data changes.

  • Choose shared credentials deliberately

    Per-user connections keep customers on their own accounts. Fixed connections serve an explicitly shared account. A fallback strategy should reflect your product’s authorization rules, not hide a missing customer connection.

  • Keep credentials on the right side

    Create connect sessions and execute API calls from a trusted backend. Your public application receives the connection flow and its outcome, rather than an organization API key.

  • Make retries specific

    Reconnect expired or revoked app access. For a write that timed out, inspect the target record before retrying. Your application still owns its business rules, deduplication and customer-facing recovery.

Apps for this workflow

Open an app to check its current actions and setup. Provider permissions and available operations vary by integration.

Build the first version.

Use the setup path that matches who will operate the workflow. Connect your accounts and verify a small task before enabling broader access.

Start from a workspace template

Preview the included apps and defaults. Templates configure a workspace; they do not install an autonomous agent or a running schedule.

Questions before you start

Do customers need a Weavz API key?

Your backend authenticates to Weavz with its API key. Customers connect their app accounts through Hosted Connect. Do not expose your backend API key in the connection flow or browser application.

Can one integration serve many customer accounts?

Yes. Configure a per-user connection strategy and identify the end user on each call. The same workspace integration alias can resolve different connected accounts for different users. Keep your application’s customer authorization checks in place.

Do I need MCP to use embedded integrations?

No. You can execute actions with the API and typed SDKs, and use supported triggers for app events. MCP is an additional interface when an AI client or agent needs to discover and use those tools.

Start with one customer and one app.

Connect an account, execute a useful action, then build the disconnect and reconnect states into your product.

Build the first integration