Prismatic Changelog

Code inputs with language: "html" or "markdown" now support rich text editing with formatting tools, a raw markup view, and a rendered preview that resolves references. Rich text inputs are supported for the embedded workflow builder, low-code designer, and embedded designer.

Additionally, new input types of number, float, date and timestamp have been introduced.

Read more about the types of inputs at Step Inputs.

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.

The Embedded Workflow Builder and low-code designer now warn you when someone else saves a newer version while you're editing. You'll see a banner with the option to reload to see the saved changes, overwrite the draft anyway, or copy the workflow. The same protection applies across multiple tabs and to Copilot.

If you embed Prismatic in your own application, the embedded SDK adds editUserLevelConfiguration(), which renders a customer user's own configuration inline so they can connect their own account without being taken through the instance's configuration. This function requires @prismatic-io/embedded version 4.14.0 or later. See opening a customer user's own configuration for implementation details.

You can now create reusable connections that are scoped to individual users, so your customers' users can connect their own accounts to third-party apps and services without needing to share credentials.

This brings together two existing concepts: User-Level Config and reusable Connections. User-level connections can now be defined outside of the scope of an integration.

Read more about user connections and how to use them in your code-native and low-code integrations.

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.

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!

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.

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.

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.