Guides

• Call any API

  Run an app action, a Function, an Endpoint or a Workflow through one call, one URL and one token — and read what comes back.

• Connect an MCP client

  Point Claude Code, Cursor or VS Code at your w6w account through the Model Context Protocol, and let a model run your Functions, Workflows and app actions.

• Aliases

  Give an action, Function, Workflow or Endpoint a short, stable name, and call it by that name instead of by ID.

• Overrides

  Reach a vendor field an app action does not declare, by merging extra detail into the outgoing request.

• Invocations

  Every call you make to an action, Function or Endpoint answers inside a frame with an id, a verdict and timing — and the call is recorded so you can look it up later.

• API health

  See whether the APIs you depend on are working — from your own call history and from the vendor's own status — and read both signals correctly.

• Spec documents

  Export a Function, Endpoint or Workflow as a portable JSON document and import it into another account — and read the report of what still needs re-connecting.

• Webhook triggers

  What a webhook delivery looks like to your workflow, which request headers are stored as [redacted], where a credential belongs, and how poll triggers check an app on an interval.

• Embed w6w in your product

  Mint an account-scoped w6w session for each signed-in user on your backend, hand it to the client, renew it before it expires, and build workflow editors on the client.

• Tenant bindings

  Pre-connect a tenantAuth app for one account of a tenant, or remove that binding, without any user entering a credential.

• Studio overview

  What Studio is, how to sign in, how the screen is laid out, and the handful of nouns every other Studio page uses.

• Sign in and projects

  Sign in to Studio with a password, a passkey, an emailed code or your organisation's SSO, sign up, and switch between or create projects.

• Publish built apps

  How CI publishes built app artifacts to a host: read the digests, post batches of artifacts, and what each per-entry outcome and error code means.

• Integrations

  Connect an API once by storing its credentials in W6W, check the connection works, and see what it can do.

• Move from OIDC to session exchange

  Switch an embedded product from direct OIDC tokens to the server-side session helper without sending any user to a different or empty account — with a read-only check to run first.

• Functions

  Give one API operation a stable name and a fixed set of inputs, bind it to an app action, and swap the vendor underneath later without changing any caller.

• Endpoints

  Give an action, Function or Workflow a stable URL that callers POST to, choose who may call it, and re-point it later without breaking anyone.

• Workflows

  Compose several API calls into one durable, multi-step run that starts on a trigger: create a workflow, declare its inputs, publish it and call it from code.

• Publish and versions

  Publish a Function, Endpoint or Workflow so callers can invoke it, look at and invoke earlier versions, roll back, disable it, archive it and delete it.

• The tool rail

  The panels on the right edge of Studio: rename and tag an item, export or import its definition, get ready-made code to call it, and set retry and failure handling.

• History

  Find any Function call, Endpoint call or workflow run in the project, filter by status, type and date, and open one to read its input, output, error and steps.

• Dashboard

  The page Studio opens on: today's and this week's workflow runs, a compact reliability board for the project, activity over time and the latest runs.

• Reliability

  See how every API your project calls is performing over the last 30 days, from your own calls and from the vendor's status page, and drill into one service's errors and latency.

• Secrets & variables

  Store plaintext, typed variables and encrypted secrets by name so steps, Functions and Endpoints can use them, and rotate a secret without touching anything that uses it.

• Documents

  Store named content such as email templates, prompts and configuration as text, Markdown, YAML, HTML or JSON, and read it from steps, Functions and code.

• Settings

  Find your way around Studio's settings, which are grouped by scope (this project, your account, your organisation, the installation), and the project's General page.