• 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.

Code-native integrations can use logger.section() and logger.sectionEnd() 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.

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.

• 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!

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

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.

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.

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.

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.

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.

Check it out in GitHub.

We've refreshed how connections are set up and managed to make reusable connections a first-class part of building an integration.

A few things to know about the new experience:

• Reusable connections are now created and managed from the Components section. Search for a component, open its Connections tab, and click + Add Connection.
• You can also create reusable connections directly from the canvas - when picking a trigger, adding a step, or from a step's connection input field.
• A pencil icon next to a step's connection lets you edit it without leaving the canvas.

Existing connections, integrations, and instances continue to work without changes.

A context pre-configures the trigger and its inputs and accepts runtime data from your application. For example, a "Create automation" button on a ticket page can create a workflow that is already wired to your "Ticket updated" trigger and scoped to that ticket's project - no blank-canvas decisions required.

Use the new prismatic.createWorkflow SDK method to create a workflow from a context, and prismatic.queryWorkflows to list workflows by context or external ID.

Additionally, you can dictate which components and actions are available to your customers when building workflows from a context, giving you more control over the experience and ensuring customers only use components that are relevant to the workflow they're building.

See Workflow contexts for setup instructions, SDK usage, and TypeScript typing support.

Key skills include a code-native integration builder, custom component builder, embed advisor for embedding the marketplace and workflow builder, migration analyzer for migrating integrations from other iPaaS platforms, and Orby - a platform expert for querying your Prismatic environment and troubleshooting.

Read more on our announcement blog post and in docs.

• Redshift - Amazon Redshift is a cloud data warehouse service. Use the component to manage clusters, execute queries, load data, and monitor warehouse performance.
• SAP ECC - SAP ECC (ERP Central Component) is an enterprise resource planning platform for managing core business processes. Use the component to manage business objects, transactions, and data across modules like finance, logistics, and human resources.
• System Surveyor - System Surveyor is a visual documentation platform for physical security and IT systems. Use the component to manage surveys, sites, devices, and floor plans.

• Datadog - Datadog is a monitoring and analytics platform for cloud-scale applications. Use the component to manage monitors, events, metrics, dashboards, and incidents.
• Salesforce Marketing Cloud - Salesforce Marketing Cloud is a digital marketing platform for managing customer journeys across email, mobile, social, and advertising channels. Use the component to manage contacts, campaigns, data extensions, and automations.
• SurveyMonkey - SurveyMonkey is a leading online survey platform that enables organizations to create surveys, collect responses, and analyze feedback at scale. Use the component to manage surveys, collectors, responses, contacts, and webhooks.
• UKG Pro - UKG Pro is a human capital management (HCM) platform. Use the component to manage employees, organizational structures, payroll data, and talent onboarding processes.

See our announcement blog post.

The copilot feature is in "Early Access" and will be generally available soon. If you'd like early access to the copilot, please reach out to your Prismatic account manager.