Skip to main content

Changelog

Prismatic Changelog

Stay up to date with the latest changes and improvements to our product.

New Components - August 2026

We are pleased to announce the following components have been recently added to the Prismatic library:

  • Oracle Fusion Cloud HCM - Oracle Fusion Cloud HCM is a cloud-based human capital management suite. Use the component to manage workers, jobs, absences, and other HR data.
  • Qualys - Qualys VMDR is a vulnerability management, detection, and response platform. Use the component to manage assets, TruRisk scores, tags, vulnerability scans, and remediation tickets.

Embedded Workflow Builder Copilot Improvements

The copilot in the embedded workflow builder has been re-architected from the ground up:

  • Faster builds: The copilot now handles many build actions at once instead of one at a time, so workflows come together with fewer round trips.
  • More reliable results. Purpose-built agents handle research, planning, building, and testing behind the scenes for more predictable behavior.
  • Context about your product. You can now give the copilot context about your product and API through the SDK, so your users get workflows built for your platform, not generic ones. Read about providing context to the copilot for details.

Nothing changes on your end. The upgrade applies automatically, the canvas stays the source of truth, and everything your users build today carries forward.

Large data syncs in the low-code designer and embedded workflow builder

Enable batching in the flow control tab

Custom connector triggers can now split the records they fetch into batches, so a flow in the low-code designer or embedded workflow builder can sync large datasets without one long-running execution doing all the work. This brings the code-native batchFlowTrigger pattern to low-code flows and embedded workflows.

This is useful when polling for new records from a third-party API, or when efficiently backfilling existing records on instance deployment.

See large data syncs in custom triggers for usage and code examples.

We've updated polling triggers in our Salesforce, HubSpot, and PostgreSQL connectors to use this new pattern, with more to come!

Improved step outputs and references in EWB and low-code

When you reference a previous step in the Embedded Workflow Builder or low-code designer, you can now see the real data that step would return, without running a test of your whole workflow. The reference panel has also been redesigned so the payload data you reference most is front and center, with less common properties tucked out of the way.

Update your custom connectors to take advantage of new step output options - read more at Step Outputs.

Authentication profiles for the prism CLI

The prism CLI now supports authentication profiles, so you can stay logged in to multiple Prismatic stacks or tenants at once. Each profile stores its own endpoint, tenant, and credentials, which makes switching between regions much simpler than juggling PRISMATIC_URL environment variables.

Create a named profile with prism login --profile <name>, then select it per command with the --profile flag, for a shell session with PRISM_PROFILE, or as your default with prism profiles:use <name>. Run prism profiles:list to view saved profiles and prism profiles:delete <name> to remove one.

See authenticating with the CLI tool for details.

Upgraded charts for at-a-glance integration health

We've rebuilt the charts across Prismatic. New interactive charts now appear on the Home page, integration landing pages, and your Customer, Instance, and Org Utilization views, so you can spot trends and jump straight to the executions behind any spike.

Toggle any chart between bar and line, and click into a day on the Executions Success/Failure chart to drill through to the underlying execution. Where available, you'll see up to 14 days of history.

New default toolchain for components and code-native integrations

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.

New Components - June 2026

We are pleased to announce the following components have been recently added to the Prismatic library:

  • Jamf - Jamf is an Apple device management platform. Use the component to manage devices, policies, scripts, and users with Jamf Pro and Jamf School.

Large data sync with batchFlowTrigger

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.

Large data sync execution results

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

Structured and dynamic object inputs for custom connectors

Custom connector actions now support two new input types that let you represent complex data directly on the canvas - no code step required.

Structured object inputs group related sub-inputs into a single named object. For example, a "Mailing Address" input can expose individual street, city, state, and zip fields rather than forcing builders to construct the object manually. In your action's perform function, the value is a plain object accessible by field name (e.g. inputs.address.city).

Dynamic object inputs show a different set of sub-inputs depending on which record type or configuration the builder selects. For example, a "Create Record" action can present Account, Lead, or Contact input fields based on the builder's choice, with inputs.record.configuration identifying the selection and inputs.record.values holding the corresponding field values.

See structured object inputs and dynamic object inputs for usage and code examples.