Embed

Put an integration catalog inside your own product. Your customers connect their own accounts, and you never build or maintain a connector.

What it is

Your customer opens a catalog that lives in your application, under your brand. They click Connect, sign in to their own Slack, GitHub or Salesforce account, and the credentials stay encrypted on work.studio — they never reach your database.

Three surfaces, from least to most work:

Surface	You write	Best for
Web component	One HTML tag	A catalog in your app, themed to match it
SDK	JavaScript	Your own interface on top of our API
REST API	HTTP	Any language, from your backend

All three talk to the same API at https://api.work.studio/api/v1/workflow/embed.

How a connection happens

%%{init: {'theme': 'base', 'themeVariables': {
  'actorTextColor': '#1e293b',
  'actorBkg': '#f1f5f9',
  'actorBorder': '#64748b',
  'signalColor': '#475569',
  'signalTextColor': '#1e293b',
  'noteBkgColor': '#fef3c7',
  'noteTextColor': '#92400e'
}}}%%

sequenceDiagram
    participant C as Your customer
    participant A as Your app
    participant S as Your server
    participant W as work.studio

    A->>S: Who is this customer?
    S->>W: Mint session token (embed key)
    W-->>S: svx_st_… token
    S-->>A: token
    A->>W: Render catalog with token
    C->>W: Connect their account
    W-->>A: svx:connection:completed

Your server holds the secret. The browser only ever sees a short-lived token bound to one customer.

The embed key is a server-side secret

An embed key (svx_ik_…) can act as any of your customers. Never put it in browser markup, a URL, or client-side JavaScript. Mint a session token from your backend instead — see Authentication.

Customer scope

Every call happens on behalf of one of your customers, identified by a scope key you choose — customer:acme, customer:42, whatever your own customer id is.

That scope is what keeps one customer's connections, automations and assistant history separate from another's. When you mint a session token you name the scope, and the token cannot act outside it.

Start here

Quick start

Web component

SDK

From an embed key to a working catalog in your page.

Quick start →

Attributes, methods and events for <svx-integration-catalog>.

Web component →

@workstudio-inc/sdk for your server and your own UI.

SDK →

Authentication

Customer MCP URLs

Keys, session tokens, scopes and the origin allowlist.

Authentication →

Let your customers' AI assistants use their own connections.

Customer MCP →

Something not behaving as described? support@work.studio