From prismatic-skills
Reference documentation for embedding Prismatic's integration marketplace and workflow builder in a web application. Covers JWT authentication, the embedded SDK, marketplace and workflow embedding, theming, i18n, additional screens, and custom marketplace UI. Use when the user asks about embedding Prismatic, JWT tokens for embedded apps, marketplace iframes, workflow builder integration, custom marketplace UI, or frontend SDK setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prismatic-skills:embedded-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reference documentation for embedding Prismatic's integration marketplace and workflow builder inside a customer-facing web application.
Reference documentation for embedding Prismatic's integration marketplace and workflow builder inside a customer-facing web application.
Embedding Prismatic means your customers never leave your app to manage integrations. The flow is:
prismatic.authenticate({ token }) with that JWT — never sign JWTs on the frontendprismatic.showMarketplace(), prismatic.showWorkflows(), or another screen method to render an embedded iframeBefore the JWT expires, the frontend re-fetches a fresh JWT from your backend and calls prismatic.authenticate({ token }) again. Existing iframes update automatically.
JWT tokens MUST be signed on your backend using your private key. Never expose the private signing key to the frontend. The frontend only receives the signed JWT string from a backend API endpoint.
Before any embedding can work, your organization needs a signing key. To check or create one:
# Check existing signing keys
prism organization:signing-keys:list --extended --output json
# Generate a new signing key (Prismatic creates the key pair)
prism organization:signing-keys:generate
# OR: import your own key generated with OpenSSL
openssl genrsa -out my-private-key.pem 4096
openssl rsa -in my-private-key.pem -pubout > my-public-key.pub
prism organization:signing-keys:import -p my-public-key.pub
The private key is only shown once at generation time — store it securely (e.g., environment variable or secrets manager). Prismatic only stores the last 8 characters of the public key for identification.
npm install @prismatic-io/embedded
import prismatic from "@prismatic-io/embedded";
// 1. Initialize once on app startup (before authentication)
prismatic.init();
// 2. Authenticate with a JWT fetched from YOUR backend
const { token } = await fetch("/api/integration-token").then(r => r.json());
await prismatic.authenticate({ token });
// 3. Show an embedded screen
prismatic.showMarketplace({ selector: "#integrations-div", usePopover: false });
Every JWT must include these Prismatic-specific fields — standard JWT libraries won't add them automatically:
| Claim | Required | Description |
|---|---|---|
sub | Yes | Unique user ID (UUID or similar) |
organization | Yes | Prismatic organization ID (from org settings → Embedded tab) |
customer | Yes | Your internal customer/tenant ID — identifies which customer this user belongs to |
iat | Yes | Issued-at Unix timestamp. Use currentTime - 5 to buffer for clock skew |
exp | Yes | Expiry Unix timestamp. Use currentTime + 600 (10 minutes) |
external_id | No | External ID for this user in Prismatic; typically matches sub |
name | No | User's display name |
customer_name | No | If no customer with this customer ID exists yet, creates one with this name |
role | No | ULC only: "admin" (can deploy) or "user" (supplies user config). Defaults to "admin". |
organization and customer are the most commonly missed fields — they are not standard JWT claims and must be set explicitly.
Minimum valid payload:
{
"sub": "user-uuid",
"organization": "T3JnYW5pemF0aW9uOi...",
"customer": "your-customer-id",
"iat": 1700000000,
"exp": 1700000600
}
exp: currentTime + 600)iat: currentTime - 5prismatic.authenticate({ token }) again ~1 minute before the token expiresprismatic.authenticate is called with a new token| Method | Purpose |
|---|---|
prismatic.init(options?) | Initialize the SDK (call once at app startup) |
prismatic.authenticate({ token }) | Authenticate with a signed JWT |
prismatic.showMarketplace(options?) | Embed the integration marketplace |
prismatic.showWorkflows(options?) | Embed the workflow builder list |
prismatic.showWorkflow({ workflowId, ...options }) | Open a specific workflow in the builder |
prismatic.createWorkflow(contextStableKey, { name, contextData, externalId }) | Create a pre-configured workflow from an org-defined context (in-app automation entry point) |
prismatic.queryWorkflows(filters?) | List the customer's workflows, filterable by context or externalId |
prismatic.showDashboard(options?) | Embed the customer dashboard |
prismatic.showConnections(options?) | Embed the connections management screen |
prismatic.showLogs(options?) | Embed the logs screen |
prismatic.showComponents(options?) | Embed the component browser |
prismatic.showComponent({ componentId, ...options }) | Show a specific component |
prismatic.configureInstance(props) | Open a config wizard for an integration |
prismatic.editInstanceConfiguration({ instanceId, selector, ... }) | Render an existing instance's config wizard inline (your own dialog/drawer) with success/cancel/delete callbacks |
prismatic.setConfigVars({ iframe, configVars }) | Programmatically set config variables |
prismatic.graphqlRequest({ query, variables? }) | Execute authenticated GraphQL queries |
Load only the references relevant to the current setup step. This keeps context focused.
references/authentication.md — Signing key setup (generate, import, list)references/authentication.md — Backend examples for Node.js, Python, Ruby, Go, C#; JWT claims referencereferences/framework-examples.md — React, Next.js, Vue, Svelte integration patterns with full codereferences/sdk-api.md — Full SDK type definitions, method signatures, ScreenConfigurationreferences/theming-and-i18n.mdreferences/theming-and-i18n.mdreferences/marketplace.mdreferences/workflow-builder.mdreferences/additional-screens.mdreferences/custom-marketplace-ui.mdFull list for manual lookup:
references/authentication.md — JWT claims, signing examples for Node.js, Python, Ruby, Go, C#, and re-authentication patternreferences/sdk-api.md — Full SDK type definitions, ScreenConfiguration, Filters, PrismaticMessageEvent enumreferences/marketplace.md — showMarketplace, filters (simple and advanced), configureInstance, editInstanceConfiguration, events, setConfigVarsreferences/workflow-builder.md — showWorkflows, showWorkflow, workflow contexts (createWorkflow, queryWorkflows), key differences from the low-code designerreferences/theming-and-i18n.md — Light/dark mode, custom fonts, loading screen, custom terms, translationsreferences/additional-screens.md — showDashboard, showConnections, showComponents, showLogs, common optionsreferences/custom-marketplace-ui.md — Building a fully custom marketplace with GraphQL, TypeScript types, avatar images, reconfiguring an existing instance inline (editInstanceConfiguration)references/framework-examples.md — React, Next.js, Vue, and Svelte integration patterns with full code examplesnpx claudepluginhub prismatic-io/prismatic-skills --plugin prismatic-skillsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.