WebinarJam / EverWebinar

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying WebinarJam / EverWebinar's real ids.

{
  "manifestVersion": "2",
  "name": "webinarjam-example",
  "steps": [
    {
      "id": "registrant-create",
      "uses": {
        "app": "io.w6w.webinarjam",
        "action": "registrant-create",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "product": "<product>",
        "webinarId": "<webinarId>",
        "schedule": "<schedule>"
      }
    }
  ]
}

Here are some of the things you can do

• Register Attendee

  perform
  registrant-create

• List Registrants

  search
  registrant-list

• Get Webinar

  read
  webinar-get

• List Webinars

  read
  webinar-list

+1 more action available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for WebinarJam / EverWebinar, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to WebinarJam / EverWebinar. The Workflow tab is where this app's real ids are.

npm install @w6w/sdk

yarn add @w6w/sdk

pnpm add @w6w/sdk

deno add npm:@w6w/sdk

import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "registrant-create",
  payload: {
    product: "<value>",
    webinarId: "<value>",
    schedule: "<value>",
    firstName: "<value>",
    // lastName: "<value>",
    email: "<value>",
    // country: "<value>",
    // state: "<value>",
    // timezoneId: "<value>",
    // ipAddress: "<value>",
    // phoneCountryCode: "<value>",
    // phone: "<value>",
    // twilioConsent: "<value>",
    // customFields: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);

npm install -g @w6w/cli

w6w run conn_YOUR_CONNECTION_ID --action registrant-create --payload '{"product":"<value>","webinarId":"<value>","schedule":"<value>","firstName":"<value>","email":"<value>"}'

Give an AI agent WebinarJam / EverWebinar — without giving it WebinarJam / EverWebinar's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.webinarjam#registrant-create",
    "input": {
      "product": "<product>",
      "webinarId": "<webinarId>",
      "schedule": "<schedule>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's WebinarJam / EverWebinar connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

The MCP surface is part of the hosted platform. WebinarJam / EverWebinar itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access