Its new embedded UI SDK enters early access: build integration setup into your own UI. Prismatic's new embedded UI SDK, now in early access, lets you build integration marketplaces, connections, and setup into your product with your own UI. Oct 15, 2026 Amrit Singh Senior Product Marketing Manager Key takeaways * Its new embedded UI SDK puts the integration experience inside your product. The integration defines what needs configuring, and your app decides how customers find, connect, and set it up, while Prismatic handles configuration state, validation, connections, deployment, and version tracking. Early access starts with headless configuration and runs through the end of October. * Built for the setup experiences that matter most. Headless fits integrations where setup should match your design system, needs more than a form can express (field mapping, lists that exist only after a connection), or replaces a hand-built setup you'd rather not maintain. * Credentials never reach your front end. Server functions declare which connection they use and run server-side, so your app only sees the function's output. Why Prismatic started with headless configuration. The hosted config wizard is how most Prismatic customers ship integrations today. You define configuration pages in the integration, Prismatic renders them, and your customers are live without you writing any setup UI. For many integrations, this path works well. And because every productized integration goes through it, it's also where Prismatic hear the most from customers. Prismatic has answered that feedback in stages. Theming let you match the wizard's colors to your UI. JSON Forms let you build custom inputs. Custom marketplaces let you own the list of integrations and how instances get created. Each step brought setup closer to your product, and each one points toward the configuration step itself. Three things customers kept asking for: Setup should be indistinguishable from your product. You have invested in a design system, onboarding patterns, and a navigation model, and your customers should get all of it when they click "Connect Salesforce." The benefits Prismatic gives you should feel like a truly native part of your product. Configuration should be as intuitive as the rest of your product, even when it's complex. JSON Forms, the hosted config wizard's option for custom inputs, has handled complex configuration well for a long time. Some experiences deserve more than a form, like: * Mapping fields between two systems. * Picking from a list that only exists after a connection is made. * A step that only makes sense once an earlier answer is known. You should be able to own the setup experience without owning the plumbing. Some teams have built their own marketplace and setup flow against its API, and it delivers exactly the presentation they want. They'd rather not handle validation, state, versioning, and every new input type themselves, and they want the Prismatic benefits that come with it. Solis, its new embedded UI SDK, delivers all three. It splits configuration into halves: the integration defines what needs to be configured, and your application decides how a customer does it. Solis enables the second half. It covers the marketplace, connections, and configuration, so a customer can find an integration, connect an account, and set it up without leaving your UI, whether that's a catalog, a connect button beside a feature, or a page of connected accounts. Headless configuration is where Prismatic is starting. Prismatic still handles configuration state, validation, connections, deployment, and version tracking underneath. How it works. Here's the shape of a headless integration, using a Slack notifications example. A user connects Slack, searches for a channel, saves it as the shared destination, and sets their own notification preference. 1. Define the configuration. Install @prismatic-io/solis-react@preview in your app and make sure you're on Prism CLI 10.6.0 or later. In the integration, one configuration definition holds the schema, a version, optional init values, and server functions. The channel belongs to the instance and the notification preference to the user, read at runtime as configuration.channelId and userConfiguration.notificationsEnabled. A listChannels server function takes the user's search text and returns matching channels using the instance's Slack connection. 2. Build your UI. In your app, useConfiguration gives you the schema, the integration's server functions, and the init and save actions. Render the form with your own components, and use useServerFunction to call listChannels as the user types. 3. Save the instance. Call save to store the values, which Prismatic validates against the schema, then deploy the instance with useInstance. Saving never deploys on its own, so a running instance keeps its old values until you deploy. The notification preference saves for the current user only, with no redeploy. To run a complete end-to-end example, follow Get Started with Headless Config. It publishes a sample CRM integration, configures it from your own app with a field mapper and live preview, and publishes an update. The example uses plain HTML controls so the SDK calls are easy to see. In your product, swap them for your own components. What early access includes. Early access is open now for customers building code-native integrations with a custom marketplace. You'll get: * The embedded UI SDK. Spectral 10.35.0 for the integration side (configuration schema, server functions, user settings, scheduling), and Solis for your app: solis-core is the framework-agnostic client, and solis-react has the hooks. Solis exposes marketplace, connection, and configuration resources today, with executions and logs to follow, so what you build on it carries forward. * Preview documentation. Examples and a migration guide for integrations that already have config pages. * Time with its team. Prismatic will check in with you throughout early access and discuss your experience. When you enable early access, your existing integrations keep working exactly as they do today, and only integrations you build with the Headless SDK will use the new model. Common questions. Amrit Singh Senior Product Marketing Manager Amrit Singh is a product marketer but an engineer at heart, helping businesses ship dev-focused products that win. At Prismatic, he helps SaaS companies turn code-first integrations and embedded workflows into product capabilities their customers rely on and grow with.

Prismatic launches new executions experience to help teams diagnose integration issues faster. Oct 01, 2026, 08:10 ET Execution sections bring step-by-step visibility to code-native runs laying the foundation for AI-assisted debugging, while rebuilt list and detail views make it faster to troubleshoot executions SIOUX FALLS, S.D., Oct. 1, 2026 /PRNewswire-PRWeb/ - Prismatic, the AI-enabled embedded iPaaS for B2B SaaS companies, today announced execution sections for code-native integrations (CNI) and a rebuilt executions experience. Execution sections give code-native integrations the step-by-step visibility already available for low-code integrations. Developers name the parts of their integration logic, and everyone who supports the integration sees which parts ran, which one failed, and the logs for each. Alongside it, rebuilt list and detail views make any run, code-native or low-code, faster to find and diagnose. Until now, a code-native integration ran as a single step. When it failed, the app showed one error and whatever the developer had logged, so troubleshooting usually went back to the person who wrote the code. That visibility gap is a reason some teams hesitate to move to code-native, even when it is the faster way to build. Execution sections narrow it. The executions page is already where teams go when a live integration breaks. A query builder finds the run behind a customer report by filtering on the trigger payload, such as an order number, and stacks conditions to isolate a pattern. A chart of successes and failures sits above the results, and clicking a bar narrows the list to that window. Open any run, and the error is stated up front, with logs and payload beneath it. "Moving to code should never mean giving up visibility," said Michael Zuercher, CEO and co-founder of Prismatic. "Execution sections make a code-native run readable to the whole team, and because code-native runs can now have structure, they become the foundation for AI that can read an execution and tell you what went wrong." Structure for code-native integrations With execution sections, developers give parts of their integration logic plain names, such as "Sync EMEA" or "Fetch files," using the Prismatic SDK. The detail view then shows the run as an ordered list of those sections with status, timing, and logs. Support and operations teams can see which section failed and open its logs, and developers see the same structure while they build and test. Sections are opt-in and require the latest version of the Prismatic SDK. Find the right execution The list view is built for filtering and triage across every customer, instance, and flow in an organization. Teams can filter by trigger payload to find the execution tied to a specific customer record, such as an order number; filter by flow across every instance it is deployed to; narrow by status and date range; and combine conditions to isolate a pattern. A chart above the results shows successes and failures over time. Once teams fix the underlying issue, they can select the affected executions and replay them together instead of one at a time. Understand what happened and why The detail view now gives each execution a dedicated page. It starts with a plain-language error, followed by a timeline of each step the execution took. Teams can expand any step to see its logs and output, view the trigger payload, replay the execution, and share a link to the run with a teammate who needs to pick it up. The release builds on visibility work Prismatic shipped earlier in 2026, including execution health charts across the app and faster log search over the full 14-day retention window. Together, they let teams see whether failures are increasing, which integration or customer is driving them, and what happened in a single run. Execution sections and the new list and detail views are now available at no additional cost. The list and detail views work for both code-native and low-code integrations. About Prismatic Prismatic is the AI-enabled embedded iPaaS for B2B SaaS companies, the foundation for product extensibility. It brings productized integrations, embedded workflows, and agentic interaction together on one core platform that handles everything that breaks at scale: authentication, deployment, monitoring, security, and compliance. Developers build and ship integrations 10x faster with code-first development and AI coding assistants. Customers build the workflows their business needs through embedded, white-labeled tools. And AI agents get the tools to take action across any connected system. Used by Fortune 500s and high-growth startups alike, Prismatic turns integrations from a bottleneck into a growth driver. Learn more at prismatic.io. Media Contact SOURCE Prismatic