You can now install Prismatic components from npm and use their actions, connections, triggers, and data sources directly in TypeScript. Each package includes the component's code and types, so you can test component calls locally and manage component versions alongside your other dependencies.

For example, install the Slack component:

npm install @prismatic-io/components-slack

The code-native getting-started tutorial now uses the Slack npm package to populate a channel dropdown and send messages. See Using Existing Components for setup requirements, examples, and package upgrades.

Component manifests are deprecated. Use npm packages whenever the component you need is available on npm. Existing manifests remain supported for backward compatibility; you can migrate one component at a time.

Solis, Prismatic's headless SDK, is now generally available. Version 0.1.0 of @prismatic-io/solis-core and @prismatic-io/solis-react is published under npm's latest tag, so you can install it without a prerelease tag:

npm install @prismatic-io/solis-react@latest

With Solis, your app presents the integration marketplace and configures headless integrations with its own UI components, such as field mappers with live previews, multi-step setup flows, and inline validation.

• Solis React (@prismatic-io/solis-react) provides hooks for React 18 and 19. See Building configuration UIs with Solis React.
• Solis Core (@prismatic-io/solis-core) works with any other framework, or none. See Installing the headless SDK.

To get started, see:

• Build a custom marketplace with Solis
• Get started with headless configuration
• Configuration presentation modes

Headless configuration is now available in early access. With headless configuration, your customers configure integrations in your app's own UI instead of Prismatic's config wizard, so you can build rich configuration experiences, like field mappers with live previews, that feel native to your product.

Headless configuration has two parts:

• In your code-native integrations, you define the shape of the configuration with a zod or JSON Schema, an init function that suggests starting values and migrates saved values between versions, and server functions your app calls for dynamic data. Prismatic validates and stores the values, and your flows read them with their real types from context.configuration. Scheduled flows can use a fixed schedule, or schedule: { fromDeployer: true } to let the customer choose the schedule while configuring. See Headless configuration.
• In your app, Solis is Prismatic's new custom UI SDK for building rich configuration experiences. Solis React (@prismatic-io/solis-react) provides hooks to list your marketplace, run an integration's server functions, and save and deploy instances, while your app renders every screen. See Solis.

To try it end to end, follow Get started with headless configuration, which walks through a Fake CRM integration and its configuration page in the example embedded app.

Headless configuration is available for code-native integrations. If you'd like early access, please reach out to your Prismatic account manager.

Executions are now split into two dedicated views to make troubleshooting faster:

• List view: Filter executions by trigger payload data with AND/OR conditions, select custom date ranges within the 14-day retention window, and replay failed executions in bulk.
• Detail view: See a plain-language error message, a step-by-step timeline, and step logs, outputs, and the trigger payload in one place.

Log search now covers the full 14-day retention window (previously 48 hours), and the default search window is now 24 hours.

Additionally, the step logs and step result experience you love from the low-code designer is now available in code-native. Code-native integrations can use logger.section() to split onExecution logic into named sections, each with its own status, timing, and logs in the detail view. Execution sections require the latest version of @prismatic-io/spectral. Read more in the Code-Native Logging and Sections documentation.

prism components:init and prism integrations:init now scaffold new projects with a new, modern toolchain for building, testing, linting, and formatting your code.

If you run into issues with the modern toolchain, you can scaffold with the previous toolchain by passing --toolchain legacy - and please contact support so we can address it.

This change ships in a new major version of the prism CLI.

Want to update an existing code-native integration or custom connector to use our new recommended toolchain? See the Spectral 10.22 Upgrade Guide for instructions.

Code-native integrations can now use batchFlowTrigger to backfill large datasets on deploy and process real-time events through the same execution path - no manual recursion required.

Define an onDeploy function to page through your source API on instance deployment, returning a paginationState cursor so each invocation picks up where the last one left off. Define an onTrigger function to handle incoming webhooks after the initial sync completes. Both funnel records into a single onExecution function, and batchConfig controls how many records arrive per call and how many batches run concurrently.

See Large Data Sync for usage and examples and here for a video walkthrough.

You can now enter listening mode when testing webhook-based triggers in code-native integrations. This allows you to quickly set up temporary webhooks in third-party applications and capture incoming webhook requests from the third-party from your IDE.

Read more in Testing Code-Native Integrations.

You can now convert low-code integrations to code-native directly within the Prismatic UI. This allows you to prototype a new integration quickly using the low-code designer, and then switch to code-native when you need more flexibility or control.

To get started, open any low-code integration and click Convert to Code. You'll get a preview of the generated code, and can choose to download a zip file containing the code-native TypeScript project.

Today we're releasing updates that significantly improve the code-native development experience on Prismatic. Build, test, and deploy integrations entirely in code with AI assistance, streamlined component management, and enhanced TypeScript support.

Prism MCP Server

• Enable AI coding assistants (Claude, Cursor) to understand Prismatic's SDK and generate integration flows, components, and test configurations using natural language

VS Code Extension

• Run test executions with detailed logs, pull existing integrations from your Prismatic instance, configure instances through embedded config wizard, and manage authentication - all without leaving your IDE

Improved Component Manifest Generation

• Generate component manifests with a single command npx cni-component-manifest <component-name> and use components without installing npm packages

Enhanced Component Referencing

• Full TypeScript support with real-time validation for defining connections, data sources, and triggers in configuration wizards

Check out the code-native development updates blog post for additional info and quick start demo videos.

Two significant improvements to code-native integrations are now out of beta:

1. You can now convert a low-code integration to code-native. This is ideal if you've built a proof-of-concept in the low-code designer, but would like the flexibility to build the rest of the integration in pure TypeScript. Learn how to convert low-code integrations to code-native.
2. As a developer, you probably want to remain in your IDE as you build and test your integration. With the prism integrations:flows:test command, you can now invoke a test of your code-native integration's flow from your terminal. Learn about testing code-native integrations from the CLI.